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>
This commit is contained in:
parent
085b0b055b
commit
2ab75df38e
@ -2072,6 +2072,9 @@ void kvm_s390_crw_mchk(void)
|
||||
.u.mchk.cr14 = 1 << 28,
|
||||
.u.mchk.mcic = 0x00400f1d40330000ULL,
|
||||
};
|
||||
if (kvm_check_extension(kvm_state, KVM_CAP_S390_VECTOR_REGISTERS)) {
|
||||
irq.u.mchk.mcic |= 0x0000004000000000ULL;
|
||||
}
|
||||
kvm_s390_floating_interrupt(&irq);
|
||||
}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user