| commit | a2689242b10a7bbc9a952659a2a5cc04a86d10e1 | |
| author | Thomas Huth <thuth@linux.vnet.ibm.com> | |
| Thu, 20 Mar 2014 20:49:18 +0000 (20 21:49 +0100) | ||
| committer | Cornelia Huck <cornelia.huck@de.ibm.com> | |
| Tue, 10 Jun 2014 07:50:27 +0000 (10 09:50 +0200) | ||
| tree | 8fa7b0018468c8eb2a6566d1f95999bdee18a4c1 | treesnapshot (tar.gz zip) |
| parent | 4cb88c3c378ae8c86c0ba53619caf6924f72239c | commitdiff |
s390x/kvm: Log unmanageable external interruptions
Interception code 0x14 only drops to userspace when an unmanageable
external interruption interception occured (e.g. if the External New
PSW does not disable external interruptions). Instead of bailing out
via the default handler, it is better to inform the user with a
proper error message that also includes the bad PSW, and to stop
the affected CPU with a panic event instead.
Signed-off-by: Thomas Huth <thuth@linux.vnet.ibm.com>
Signed-off-by: Jens Freimann <jfrei@linux.vnet.ibm.com>
Reviewed-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Interception code 0x14 only drops to userspace when an unmanageable
external interruption interception occured (e.g. if the External New
PSW does not disable external interruptions). Instead of bailing out
via the default handler, it is better to inform the user with a
proper error message that also includes the bad PSW, and to stop
the affected CPU with a panic event instead.
Signed-off-by: Thomas Huth <thuth@linux.vnet.ibm.com>
Signed-off-by: Jens Freimann <jfrei@linux.vnet.ibm.com>
Reviewed-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
| target-s390x/kvm.c | diffblobblamehistory |