Collin Walling c35aff184b s390: kvm: adjust diag318 resets to retain data ... The CPNC portion of the diag318 data is erroneously reset during an initial CPU reset caused by SIGP. Let's go ahead and relocate the diag318_info field within the CPUS390XState struct such that it is only zeroed during a clear reset. This way, the CPNC will be retained for each VCPU in the configuration after the diag318 instruction has been invoked. The s390_machine_reset code already takes care of zeroing the diag318 data on VM resets, which also cover resets caused by diag308. Fixes: fabdada935 ("s390: guest support for diagnose 0x318") Reported-by: Christian Borntraeger <borntraeger@de.ibm.com> Signed-off-by: Collin Walling <walling@linux.ibm.com> Reviewed-by: Janosch Frank <frankja@linux.ibm.com> Reviewed-by: Christian Borntraeger <borntraeger@linux.ibm.com> Message-Id: <20211117152303.627969-1-walling@linux.ibm.com> Signed-off-by: Thomas Huth <thuth@redhat.com>		2021-12-17 09:12:37 +01:00
..
kvm.c	s390: kvm: adjust diag318 resets to retain data	2021-12-17 09:12:37 +01:00
kvm_s390x.h	target/s390x: move kvm files into kvm/	2021-07-07 14:01:59 +02:00
meson.build	target/s390x: move kvm files into kvm/	2021-07-07 14:01:59 +02:00
trace-events	target/s390x: move kvm files into kvm/	2021-07-07 14:01:59 +02:00
trace.h	target/s390x: move kvm files into kvm/	2021-07-07 14:01:59 +02:00