From: Jarkko Sakkinen <jarkko@kernel.org>
To: Sean Christopherson <seanjc@google.com>
Cc: Dave Hansen <dave.hansen@intel.com>,
Kai Huang <kai.huang@intel.com>,
dave.hansen@linux.intel.com, linux-sgx@vger.kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
pbonzini@redhat.com, haitao.huang@linux.intel.com
Subject: Re: [PATCH v2] x86/sgx: Allow exposing EDECCSSA user leaf function to KVM guest
Date: Thu, 25 Aug 2022 22:27:37 +0300 [thread overview]
Message-ID: <YwfNKePFxyeRtscl@kernel.org> (raw)
In-Reply-To: <YweaEl48I7pxKMm8@google.com>
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
next prev parent reply other threads:[~2022-08-25 19:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 2:38 [PATCH v2] x86/sgx: Allow exposing EDECCSSA user leaf function to KVM guest 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 [this message]
2022-08-29 1:37 ` Huang, Kai
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=YwfNKePFxyeRtscl@kernel.org \
--to=jarkko@kernel.org \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=haitao.huang@linux.intel.com \
--cc=kai.huang@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.