s390x/kvm: Fix vector validity bit in device machine checks
commit2ab75df38e34fe9bc271b5115ab52114e6e63a89
authorChristian Borntraeger <borntraeger@de.ibm.com>
Wed, 7 Oct 2015 08:29:42 +0000 (7 10:29 +0200)
committerCornelia Huck <cornelia.huck@de.ibm.com>
Tue, 20 Oct 2015 14:21:00 +0000 (20 16:21 +0200)
tree940934d53073989d9a3061d4c1e9fb8fd78a5ee6
parent085b0b055b189e8846ca3108e6774e3b9e60c1ce
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>
target-s390x/kvm.c