[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4efdfef972073eb927150c528487d22373bef4d3.camel@intel.com>
Date: Wed, 27 Jul 2022 09:23:24 +1200
From: Kai Huang <kai.huang@...el.com>
To: Dave Hansen <dave.hansen@...el.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, dave@...1.net
Cc: Jarkko Sakkinen <jarkko@...nel.org>,
Andy Lutomirski <luto@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>,
Sean Christopherson <seanjc@...gle.com>,
Haitao Huang <haitao.huang@...ux.intel.com>, x86@...nel.org,
linux-sgx@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [v2] x86/sgx: Allow enclaves to use Asynchrounous Exit
Notification
On Tue, 2022-07-26 at 08:36 -0700, Dave Hansen wrote:
> On 7/22/22 06:26, Kai Huang wrote:
> > Did a quick look at the spec. It appears ENCLU[EDECCSSA] should be used
> > together with AEX-notify. So besides advertising the new
> > SGX_ATTR_ASYNC_EXIT_NOTIFY bit to the KVM guest, I think we should also
> > advertise the ENCLU[EDECCSSA] support in guest's CPUID, like below (untested)?
>
> Kai, would you care to send a new version of this with a proper SoB and
> changelog integrating what you've learned since posting it? It can be
> merged along with AEX notify itself.
Sure will do today.
--
Thanks,
-Kai
Powered by blists - more mailing lists