[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8db47bc1-445b-49db-b932-96aff0eb58a9@intel.com>
Date: Tue, 29 Apr 2025 07:46:01 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: "Reshetova, Elena" <elena.reshetova@...el.com>,
Sean Christopherson <seanjc@...gle.com>
Cc: "jarkko@...nel.org" <jarkko@...nel.org>, "Huang, Kai"
<kai.huang@...el.com>, "linux-sgx@...r.kernel.org"
<linux-sgx@...r.kernel.org>,
"Scarlata, Vincent R" <vincent.r.scarlata@...el.com>,
"x86@...nel.org" <x86@...nel.org>, "Annapurve, Vishal"
<vannapurve@...gle.com>, "Cai, Chong" <chongc@...gle.com>,
"Mallick, Asit K" <asit.k.mallick@...el.com>,
"Aktas, Erdem" <erdemaktas@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"bondarn@...gle.com" <bondarn@...gle.com>,
"dionnaglaze@...gle.com" <dionnaglaze@...gle.com>,
"Raynor, Scott" <scott.raynor@...el.com>
Subject: Re: [PATCH v3 2/2] x86/sgx: Implement EUPDATESVN and
opportunistically call it during first EPC page alloc
On 4/29/25 04:44, Reshetova, Elena wrote:
>> On 4/25/25 14:58, Sean Christopherson wrote:
>>> On Fri, Apr 25, 2025, Dave Hansen wrote:
>>>> On 4/25/25 14:04, Sean Christopherson wrote:
>>>>> Userspace is going to be waiting on ->release() no matter what.
>>>> Unless it isn't even involved and it happens automatically.
>>> With my Google hat on: no thanks.
>> I'm completely open to the idea of adding transparency so that folks can
>> tell when the SVN increments. I'm mostly open to having a new ABI to do
>> it explicitly in addition to doing it implicitly.]
> Could you please clarify here Dave what ABI do you have in mind?
I should have said I'm open to *eventually* adding features and new ABI
to prod at the SVN state.
Not now.
Powered by blists - more mailing lists