[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM8PR11MB5750CBAFDCC9388A100E2E95E7812@DM8PR11MB5750.namprd11.prod.outlook.com>
Date: Mon, 28 Apr 2025 06:25:27 +0000
From: "Reshetova, Elena" <elena.reshetova@...el.com>
To: Sean Christopherson <seanjc@...gle.com>
CC: "jarkko@...nel.org" <jarkko@...nel.org>, "Huang, Kai"
<kai.huang@...el.com>, "Hansen, Dave" <dave.hansen@...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
> So then why on earth is the kernel implementing automatic updates? 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.
>
> Even worse, rejecting enclave creation on EUPDATESVN failure represents an
> ABI
> change, i.e. could break existing setups.
>
> Why not simply add an ioctl() or sysfs knob to let userspace trigger
> EUPDATESVN?
Just for the record, this was my initial proposal on how to do this :)
So, I personally agree with this line of thinking fully.
Best Regards,
Elena.
Powered by blists - more mailing lists