From: Tom Lendacky <thomas.lendacky@amd.com>
To: Peter Gonda <pgonda@google.com>, kvm@vger.kernel.org
Cc: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Joerg Roedel <joro@8bytes.org>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] KVM: SEV: Update SEV-ES shutdown intercepts with more metadata
Date: Thu, 7 Sep 2023 16:56:46 -0500 [thread overview]
Message-ID: <2b6b1ae1-d209-edc9-76ab-15a17c23f038@amd.com> (raw)
In-Reply-To: <20230907162449.1739785-1-pgonda@google.com>
On 9/7/23 11:24, Peter Gonda wrote:
> Currently if an SEV-ES VM shuts down userspace sees KVM_RUN struct with
> only the INVALID_ARGUMENT. This is a very limited amount of information
> to debug the situation. Instead KVM can return a
> KVM_EXIT_SHUTDOWN to alert userspace the VM is shutting down and
> is not usable any further.
>
> Signed-off-by: Peter Gonda <pgonda@google.com>
> Suggested-by: Sean Christopherson <seanjc@google.com>
> Suggested-by: Tom Lendacky <thomas.lendacky@amd.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Sean Christopherson <seanjc@google.com>
> Cc: Tom Lendacky <thomas.lendacky@amd.com>
> Cc: Joerg Roedel <joro@8bytes.org>
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: x86@kernel.org
> Cc: kvm@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
> ---
> arch/x86/kvm/svm/svm.c | 15 +++++++--------
> 1 file changed, 7 insertions(+), 8 deletions(-)
>
> diff --git a/arch/x86/kvm/svm/svm.c b/arch/x86/kvm/svm/svm.c
> index 956726d867aa..114afc897465 100644
> --- a/arch/x86/kvm/svm/svm.c
> +++ b/arch/x86/kvm/svm/svm.c
> @@ -2127,12 +2127,6 @@ static int shutdown_interception(struct kvm_vcpu *vcpu)
> struct kvm_run *kvm_run = vcpu->run;
> struct vcpu_svm *svm = to_svm(vcpu);
>
> - /*
> - * The VM save area has already been encrypted so it
> - * cannot be reinitialized - just terminate.
> - */
> - if (sev_es_guest(vcpu->kvm))
> - return -EINVAL;
>
> /*
> * VMCB is undefined after a SHUTDOWN intercept. INIT the vCPU to put
> @@ -2141,9 +2135,14 @@ static int shutdown_interception(struct kvm_vcpu *vcpu)
> * userspace. At a platform view, INIT is acceptable behavior as
> * there exist bare metal platforms that automatically INIT the CPU
> * in response to shutdown.
> + *
> + * The VM save area for SEV-ES guests has already been encrypted so it
> + * cannot be reinitialized, i.e. synthesizing INIT is futile.
> */
> - clear_page(svm->vmcb);
> - kvm_vcpu_reset(vcpu, true);
> + if (!sev_es_guest(vcpu->kvm)) {
> + clear_page(svm->vmcb);
> + kvm_vcpu_reset(vcpu, true);
> + }
>
> kvm_run->exit_reason = KVM_EXIT_SHUTDOWN;
> return 0;
next prev parent reply other threads:[~2023-09-07 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 16:24 Peter Gonda
2023-09-07 21:56 ` Tom Lendacky [this message]
2023-09-29 2:21 ` Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2b6b1ae1-d209-edc9-76ab-15a17c23f038@amd.com \
--to=thomas.lendacky@amd.com \
--cc=bp@alien8.de \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=pgonda@google.com \
--cc=seanjc@google.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®