From: "Huang, Kai" <kai.huang@intel.com>
To: "jarkko@kernel.org" <jarkko@kernel.org>, "Christopherson,,
Sean" <seanjc@google.com>
Cc: "linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"haitao.huang@linux.intel.com" <haitao.huang@linux.intel.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>
Subject: Re: [PATCH v2] x86/sgx: Allow exposing EDECCSSA user leaf function to KVM guest
Date: Mon, 29 Aug 2022 01:37:13 +0000 [thread overview]
Message-ID: <6ae8a6ede768315c43f3dd224d339c4c41c3e445.camel@intel.com> (raw)
In-Reply-To: <YwfNKePFxyeRtscl@kernel.org>
On Thu, 2022-08-25 at 22:27 +0300, Jarkko Sakkinen wrote:
> On Thu, Aug 25, 2022 at 03:49:38PM +0000, Sean Christopherson wrote:
> > On Thu, Aug 25, 2022, Dave Hansen wrote:
> > > On 8/25/22 08:19, Sean Christopherson wrote:
> > > > > > This patch, along with your patch to expose AEX-notify attribute bit to
> > > > > > guest, have been tested that both AEX-notify and EDECCSSA work in the VM.
> > > > > > Feel free to merge this patch.
> > > > Dave, any objection to taking this through the KVM tree?
> > >
> > > This specific patch? Or are you talking about the couple of AEX-notify
> > > patches in their entirety?
> >
> > I was thinking just this specific patch, but I temporarily forgot there are more
> > patches in flight. It would be a bit odd to have effectively half of the AEX-notify
> > enabling go through KVM.
> >
> > So with shortlog/changelog tweaks,
> >
> > Acked-by: Sean Christopherson <seanjc@google.com>
>
> with subsystem tag change (Sean's version):
>
> Acked-by: Jarkko Sakkinen <jarkko@kernel.org>
>
> BR, Jarkko
Thanks. Will send out a new version with updated title and changelog.
--
Thanks,
-Kai
next prev parent reply other threads:[~2022-08-29 1:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 2:38 Kai Huang
2022-08-25 3:26 ` Jarkko Sakkinen
2022-08-25 3:27 ` Jarkko Sakkinen
2022-08-25 15:19 ` Sean Christopherson
2022-08-25 15:44 ` Dave Hansen
2022-08-25 15:49 ` Sean Christopherson
2022-08-25 19:27 ` Jarkko Sakkinen
2022-08-29 1:37 ` Huang, Kai [this message]
2022-08-29 1:36 ` Huang, Kai
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=6ae8a6ede768315c43f3dd224d339c4c41c3e445.camel@intel.com \
--to=kai.huang@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=haitao.huang@linux.intel.com \
--cc=jarkko@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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
all inboxes | Powered by JetHome®