| commit | 7c22dcdeb85dc8b1eb5f923e4c075d3046750513 | |
| author | Christian Borntraeger <borntraeger@de.ibm.com> | |
| Wed, 7 Oct 2015 08:29:42 +0000 (7 10:29 +0200) | ||
| committer | Michael Roth <mdroth@linux.vnet.ibm.com> | |
| Wed, 21 Oct 2015 16:26:52 +0000 (21 11:26 -0500) | ||
| tree | 342b591b55910a839d5c1accf8d666786b7b28c1 | treesnapshot (tar.gz zip) |
| parent | 16514367efea1172e7b702c61c6f5637bf577f5b | commitdiff |
s390x/kvm: Fix vector validity bit in device machine checks
Device hotplugs trigger a crw machine check. All machine checks
have validity bits for certain register types. With vector support
we also have to claim that vector registers are valid.
This is a band-aid suitable for stable. Long term we should
create the full mcic value dynamically depending on the active
features in the kernel interrupt handler.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: qemu-stable@nongnu.org
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
(cherry picked from commit 2ab75df38e34fe9bc271b5115ab52114e6e63a89)
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Device hotplugs trigger a crw machine check. All machine checks
have validity bits for certain register types. With vector support
we also have to claim that vector registers are valid.
This is a band-aid suitable for stable. Long term we should
create the full mcic value dynamically depending on the active
features in the kernel interrupt handler.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: qemu-stable@nongnu.org
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
(cherry picked from commit 2ab75df38e34fe9bc271b5115ab52114e6e63a89)
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
| target-s390x/kvm.c | diffblobblamehistory |