aboutsummaryrefslogtreecommitdiff
path: root/scripts/check_sparse.py
diff options
context:
space:
mode:
authorMichael Roth <michael.roth@amd.com>2024-04-09 18:07:41 -0500
committerPaolo Bonzini <pbonzini@redhat.com>2024-04-23 17:35:25 +0200
commit023267334da375226720e62963df9545aa8fc2fd (patch)
tree4df5704ddbb9198ad87b7dbe9c98783b9a83d649 /scripts/check_sparse.py
parent663e2f443e5722370708ce2f4c27d94a2087d2d3 (diff)
downloadqemu-023267334da375226720e62963df9545aa8fc2fd.zip
qemu-023267334da375226720e62963df9545aa8fc2fd.tar.gz
qemu-023267334da375226720e62963df9545aa8fc2fd.tar.bz2
i386/sev: Add 'legacy-vm-type' parameter for SEV guest objects
QEMU will currently automatically make use of the KVM_SEV_INIT2 API for initializing SEV and SEV-ES guests verses the older KVM_SEV_INIT/KVM_SEV_ES_INIT interfaces. However, the older interfaces will silently avoid sync'ing FPU/XSAVE state to the VMSA prior to encryption, thus relying on behavior and measurements that assume the related fields to be allow zero. With KVM_SEV_INIT2, this state is now synced into the VMSA, resulting in measurements changes and, theoretically, behaviorial changes, though the latter are unlikely to be seen in practice. To allow a smooth transition to the newer interface, while still providing a mechanism to maintain backward compatibility with VMs created using the older interfaces, provide a new command-line parameter: -object sev-guest,legacy-vm-type=true,... and have it default to false. Signed-off-by: Michael Roth <michael.roth@amd.com> Message-ID: <20240409230743.962513-2-michael.roth@amd.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/check_sparse.py')
0 files changed, 0 insertions, 0 deletions