summaryrefslogtreecommitdiff
path: root/drivers/tty
diff options
context:
space:
mode:
authorQingFeng Hao <haoqf@linux.vnet.ibm.com>2017-06-07 12:41:19 +0300
committerChristian Borntraeger <borntraeger@de.ibm.com>2017-06-27 17:05:38 +0300
commitda72ca4d4090a8ab0e6b0a23682ef42d39d7ae00 (patch)
tree6ebff6f83cbc639d76554660494d42f83c60c08e /drivers/tty
parentc929500d7a5aaea4f2eeba10816bc5341c66ae57 (diff)
downloadlinux-da72ca4d4090a8ab0e6b0a23682ef42d39d7ae00.tar.xz
KVM: s390: Backup the guest's machine check info
When a machine check happens in the guest, related mcck info (mcic, external damage code, ...) is stored in the vcpu's lowcore on the host. Then the machine check handler's low-level part is executed, followed by the high-level part. If the high-level part's execution is interrupted by a new machine check happening on the same vcpu on the host, the mcck info in the lowcore is overwritten with the new machine check's data. If the high-level part's execution is scheduled to a different cpu, the mcck info in the lowcore is uncertain. Therefore, for both cases, the further reinjection to the guest will use the wrong data. Let's backup the mcck info in the lowcore to the sie page for further reinjection, so that the right data will be used. Add new member into struct sie_page to store related machine check's info of mcic, failing storage address and external damage code. Signed-off-by: QingFeng Hao <haoqf@linux.vnet.ibm.com> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Diffstat (limited to 'drivers/tty')
0 files changed, 0 insertions, 0 deletions