On 2/26/20 4:00 PM, Christian Borntraeger wrote: > > > On 26.02.20 13:20, Janosch Frank wrote: >> As we now have access to the protection state of the cpus, we can >> implement special handling of diag 308 subcodes for cpus in the >> protected state. >> >> For subcodes 0 and 1 we need to unshare all pages before continuing, >> so the guest doesn't accidentally expose data when dumping. >> >> For subcode 3/4 we tear down the protected VM and reboot into >> unprotected mode. We do not provide a secure reboot. >> >> Before we can do the unshare calls, we need to mark all cpus as >> stopped. >> >> Signed-off-by: Janosch Frank <[email protected]> >> --- >> hw/s390x/s390-virtio-ccw.c | 37 ++++++++++++++++++++++++++++++++++--- >> target/s390x/diag.c | 4 ++++ >> 2 files changed, 38 insertions(+), 3 deletions(-) >> >> diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c >> index 79f472c309..9983165b05 100644 >> --- a/hw/s390x/s390-virtio-ccw.c >> +++ b/hw/s390x/s390-virtio-ccw.c >> @@ -335,6 +335,7 @@ static void s390_machine_unprotect(S390CcwMachineState >> *ms) >> } >> ms->pv = false; >> } >> + migrate_del_blocker(pv_mig_blocker); >> } >> > > and that part into patch 5? > >
Already fixed in the branch :-)
signature.asc
Description: OpenPGP digital signature
