From: Paolo Bonzini <pbonzini@redhat.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org
Cc: Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Brijesh Singh <brijesh.singh@amd.com>
Subject: Re: [PATCH] KVM: SVM: Do not terminate SEV-ES guests on GHCB validation failure
Date: Thu, 2 Dec 2021 20:39:56 +0100 [thread overview]
Message-ID: <bcb33845-6fff-34c1-9e41-fb611b6f9319@redhat.com> (raw)
In-Reply-To: <b0443caf-d822-f671-d930-ff317833d701@amd.com>
On 12/2/21 20:39, Tom Lendacky wrote:
>> Queued, thanks. Though it would have been nicer to split the changes
>> in the return values (e.g. for setup_vmgexit_scratch and
>> sev_es_validate_vmgexit) from the introduction of the new GHCB exitinfo.
>
> I can still do that if it will help make things easier. Let me know.
Well, at this point I've already reviewed it. :)
Paolo
next prev parent reply other threads:[~2021-12-02 19:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 18:52 Tom Lendacky
2021-12-02 19:19 ` Paolo Bonzini
2021-12-02 19:39 ` Tom Lendacky
2021-12-02 19:39 ` Paolo Bonzini [this message]
2021-12-03 16:39 ` Sean Christopherson
2021-12-03 18:59 ` Tom Lendacky
2021-12-03 19:22 ` Sean Christopherson
2021-12-03 22:46 ` Tom Lendacky
2021-12-04 5:14 ` Marc Orr
-- strict thread matches above, loose matches on Subject: below --
2021-05-14 19:22 Tom Lendacky
2021-05-14 23:06 ` Peter Gonda
2021-05-17 15:08 ` Tom Lendacky
2021-05-20 19:16 ` Sean Christopherson
2021-05-20 19:27 ` Sean Christopherson
2021-05-20 20:22 ` Sean Christopherson
2021-05-20 21:04 ` Tom Lendacky
2021-05-20 20:57 ` Tom Lendacky
2021-05-27 17:22 ` Sean Christopherson
2021-07-21 12:32 ` Vitaly Kuznetsov
2021-07-21 20:09 ` 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=bcb33845-6fff-34c1-9e41-fb611b6f9319@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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®