From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Wanpeng Li <kernellwp@gmail.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm <kvm@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH] KVM: x86: Add kvm_x86_ops hook to short circuit emulation
Date: Tue, 29 Sep 2020 18:43:17 -0700 [thread overview]
Message-ID: <20200930014317.GG32531@linux.intel.com> (raw)
In-Reply-To: <2cacbe0d-703b-cb06-ac5b-96841f145b95@redhat.com>
On Tue, Sep 22, 2020 at 03:32:58PM +0200, Paolo Bonzini wrote:
> On 16/09/20 19:34, Sean Christopherson wrote:
> >
> > The intent of posting the patch standalone is so that SGX, SEV-ES, and/or TDX
> > have "ready to go" support in upstream, i.e. can change only the VMX/SVM
> > implementation of is_emulated(). I'm a-ok dropping the handle_ud() change,
> > or even the whole patch, until one of the above three is actually ready for
> > inclusion.
>
> I think it's fine with the "can" in the name. Hopefully one of the
> three will go in soon...
FWIW, the changelog still references is_emulated(). Probably not worth
rewriting history though.
next prev parent reply other threads:[~2020-09-30 1:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 23:27 [PATCH] KVM: x86: Add kvm_x86_ops hook to short circuit emulation Sean Christopherson
2020-09-16 1:31 ` Wanpeng Li
2020-09-16 17:34 ` Sean Christopherson
2020-09-22 13:32 ` Paolo Bonzini
2020-09-30 1:43 ` Sean Christopherson [this message]
2020-09-22 13:32 ` Paolo Bonzini
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=20200930014317.GG32531@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=thomas.lendacky@amd.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
/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