From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Michael Roth <michael.roth@amd.com>
Cc: kvm@vger.kernel.org, Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org,
Tom Lendacky <thomas.lendacky@amd.com>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH v2] KVM: SVM: use vmsave/vmload for saving/restoring additional host state
Date: Thu, 17 Dec 2020 09:29:27 +0100 [thread overview]
Message-ID: <93168eba-6139-2d01-f8a5-182ecd723a8e@redhat.com> (raw)
In-Reply-To: <X9qcsq2kW1kkoVWI@google.com>
On 17/12/20 00:48, Sean Christopherson wrote:
>> c) refactor SEV-ES handling as part of this series. it's only a small change
>> to the SEV-ES code but it re-orders enough things around that I'm
>> concerned it might invalidate some of the internal testing we've done.
>> whereas a follow-up refactoring such as the above options can be rolled
>> into our internal testing so we can let our test teams re-verify
>>
>> Obviously I prefer b) but I'm biased on the matter and fine with whatever
>> you and others think is best. I just wanted to point out my concerns with
>> the various options.
> Definitely (c). This has already missed 5.11 (unless Paolo plans on shooting
> from the hip),
No, 5.11 is more or less done as far as x86 is concerned. I'm sending
the PR to Linus right now.
Paolo
> which means SEV-ES will get to enjoy a full (LTS) kernel release
> before these optimizations take effect.
prev parent reply other threads:[~2020-12-17 8:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 17:41 [PATCH v2] KVM: SVM: use vmsave/vmload for saving/restoring additional host state Michael Roth
2020-12-14 19:38 ` Sean Christopherson
2020-12-14 20:08 ` Andy Lutomirski
2020-12-14 22:02 ` Michael Roth
2020-12-14 22:23 ` Sean Christopherson
2020-12-14 22:29 ` Andy Lutomirski
2020-12-15 10:15 ` Paolo Bonzini
2020-12-15 18:17 ` Michael Roth
2020-12-16 15:12 ` Michael Roth
2020-12-16 15:23 ` Paolo Bonzini
2020-12-16 17:07 ` Michael Roth
2020-12-15 18:55 ` Michael Roth
2020-12-16 23:48 ` Sean Christopherson
2020-12-17 8:29 ` Paolo Bonzini [this message]
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=93168eba-6139-2d01-f8a5-182ecd723a8e@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=michael.roth@amd.com \
--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;
as well as URLs for NNTP newsgroup(s).