[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0d7d6b9a-e7bd-4225-8f08-05bd9473a894@intel.com>
Date: Fri, 25 Apr 2025 11:04:56 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Sean Christopherson <seanjc@...gle.com>,
Elena Reshetova <elena.reshetova@...el.com>
Cc: "jarkko@...nel.org" <jarkko@...nel.org>, Kai Huang <kai.huang@...el.com>,
"linux-sgx@...r.kernel.org" <linux-sgx@...r.kernel.org>,
Vincent Scarlata <vincent.r.scarlata@...el.com>,
"x86@...nel.org" <x86@...nel.org>, Vishal Annapurve <vannapurve@...gle.com>,
Chong Cai <chongc@...gle.com>, Asit K Mallick <asit.k.mallick@...el.com>,
Erdem Aktas <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>,
Scott Raynor <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/25/25 10:40, Sean Christopherson wrote:
> So then why on earth is the kernel implementing automatic updates?
Because it's literally the least amount of code and doesn't create any
new ABI.
> I read back through most of the cover letters, and IIUC, we went
> straight from "destroy all enclaves and force an update" to "blindly
> try to do EUPDATESVN every time the number of enclaves goes from
> 0=>1". Those are essentially the two most extreme options.
I'm sure we can think of a bunch more extreme things. How about after
every ENCLS? ;)
Powered by blists - more mailing lists