diff options
| author | Sean Christopherson <[email protected]> | 2025-02-27 01:25:35 +0000 |
|---|---|---|
| committer | Sean Christopherson <[email protected]> | 2025-03-03 15:33:44 +0000 |
| commit | d26638bfcdfc5c8c4e085dc3f5976a0443abab3c (patch) | |
| tree | f3032d029107af2a3349cd4ac37e106db6b8cd01 /tools/testing/selftests/net/lib/py/utils.py | |
| parent | KVM: SVM: Refuse to attempt VRMUN if an SEV-ES+ guest has an invalid VMSA (diff) | |
| download | kernel-d26638bfcdfc5c8c4e085dc3f5976a0443abab3c.tar.gz kernel-d26638bfcdfc5c8c4e085dc3f5976a0443abab3c.zip | |
KVM: SVM: Don't change target vCPU state on AP Creation VMGEXIT error
If KVM rejects an AP Creation event, leave the target vCPU state as-is.
Nothing in the GHCB suggests the hypervisor is *allowed* to muck with vCPU
state on failure, let alone required to do so. Furthermore, kicking only
in the !ON_INIT case leads to divergent behavior, and even the "kick" case
is non-deterministic.
E.g. if an ON_INIT request fails, the guest can successfully retry if the
fixed AP Creation request is made prior to sending INIT. And if a !ON_INIT
fails, the guest can successfully retry if the fixed AP Creation request is
handled before the target vCPU processes KVM's
KVM_REQ_UPDATE_PROTECTED_GUEST_STATE.
Fixes: e366f92ea99e ("KVM: SEV: Support SEV-SNP AP Creation NAE event")
Cc: [email protected]
Reviewed-by: Tom Lendacky <[email protected]>
Reviewed-by: Pankaj Gupta <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Diffstat (limited to 'tools/testing/selftests/net/lib/py/utils.py')
0 files changed, 0 insertions, 0 deletions