Messages in this thread | | | Date | Mon, 21 Mar 2022 16:27:43 +0100 | Subject | Re: [PATCH] Add KVM_EXIT_SHUTDOWN metadata for SEV-ES | From | Paolo Bonzini <> |
| |
On 3/21/22 16:02, Peter Gonda wrote: > SEV-ES guests can request termination using the GHCB's MSR protocol. See > AMD's GHCB spec section '4.1.13 Termination Request'. Currently when a > guest does this the userspace VMM sees an KVM_EXIT_UNKNOWN (-EVINAL) > return code from KVM_RUN. By adding a KVM_EXIT_SHUTDOWN_ENTRY to kvm_run > struct the userspace VMM can clearly see the guest has requested a SEV-ES > termination including the termination reason code set and reason code. > > Signed-off-by: Peter Gonda <pgonda@google.com> > Cc: Borislav Petkov <bp@alien8.de> > Cc: Tom Lendacky <thomas.lendacky@amd.com> > Cc: Brijesh Singh <brijesh.singh@amd.com> > Cc: Joerg Roedel <jroedel@suse.de> > Cc: Marc Orr <marcorr@google.com> > Cc: Sean Christopherson <seanjc@google.com> > Cc: kvm@vger.kernel.org > Cc: linux-kernel@vger.kernel.org
Looks good, but it has to also add a capability.
> + /* KVM_EXIT_SHUTDOWN_ENTRY */
Just KVM_EXIT_SHUTDOWN.
Paolo
> + struct { > + __u64 reason; > + __u32 ndata; > + __u64 data[16]; > + } shutdown; > /* KVM_EXIT_FAIL_ENTRY */ > struct { > __u64 hardware_entry_failure_reason;
| |