mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Huang, Kai" <kai.huang@intel.com>
To: "Reshetova, Elena" <elena.reshetova@intel.com>,
	"Hansen, Dave" <dave.hansen@intel.com>
Cc: "seanjc@google.com" <seanjc@google.com>,
	"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"Scarlata, Vincent R" <vincent.r.scarlata@intel.com>,
	"Raynor, Scott" <scott.raynor@intel.com>,
	"Annapurve, Vishal" <vannapurve@google.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Mallick, Asit K" <asit.k.mallick@intel.com>,
	"Aktas, Erdem" <erdemaktas@google.com>,
	"Cai, Chong" <chongc@google.com>,
	"bondarn@google.com" <bondarn@google.com>,
	"jarkko@kernel.org" <jarkko@kernel.org>,
	"dionnaglaze@google.com" <dionnaglaze@google.com>
Subject: Re: [PATCH v5 3/5] x86/sgx: Define error codes for use by ENCLS[EUPDATESVN]
Date: Mon, 19 May 2025 11:36:09 +0000	[thread overview]
Message-ID: <5bdc23827265d1aa53a8e30314dbb049c424c3a9.camel@intel.com> (raw)
In-Reply-To: <DM8PR11MB5750D757F7218259CEE77387E79CA@DM8PR11MB5750.namprd11.prod.outlook.com>

On Mon, 2025-05-19 at 11:30 +0000, Reshetova, Elena wrote:
> > On Mon, 2025-05-19 at 10:24 +0300, Elena Reshetova wrote:
> > > Add error codes for ENCLS[EUPDATESVN], then SGX CPUSVN update
> > > process can know the execution state of EUPDATESVN and notify
> > > userspace.
> > > 
> > > Signed-off-by: Elena Reshetova <elena.reshetova@intel.com>
> > > ---
> > 
> > [...]
> > 
> > > 
> > >  /**
> > > @@ -73,6 +74,11 @@ enum sgx_encls_function {
> > >   *				public key does not match
> > IA32_SGXLEPUBKEYHASH.
> > >   * %SGX_PAGE_NOT_MODIFIABLE:	The EPC page cannot be modified
> > because it
> > >   *				is in the PENDING or MODIFIED state.
> > > + * %SGX_INSUFFICIENT_ENTROPY:	Insufficient entropy in RNG.
> > > + * %SGX_EPC_NOT_READY:			EPC is not ready for SVN
> > update.
> > > + * %SGX_NO_UPDATE:		EUPDATESVN was successful, but
> > CPUSVN was not
> > > + *				updated because current SVN was not newer
> > than
> > > + *				CPUSVN.
> > >   * %SGX_UNMASKED_EVENT:		An unmasked event, e.g. INTR, was
> > received
> > >   */
> > >  enum sgx_return_code {
> > > @@ -81,6 +87,9 @@ enum sgx_return_code {
> > >  	SGX_CHILD_PRESENT		= 13,
> > >  	SGX_INVALID_EINITTOKEN		= 16,
> > >  	SGX_PAGE_NOT_MODIFIABLE		= 20,
> > > +	SGX_INSUFFICIENT_ENTROPY	= 29,
> > > +	SGX_EPC_NOT_READY			= 30,
> > > +	SGX_NO_UPDATE				= 31,
> > >  	SGX_UNMASKED_EVENT		= 128,
> > >  };
> > > 
> > 
> > It doesn't seem SGX_EPC_NOT_READY is used in this series.
> 
> 
> You are right, not anymore. However, it is a valid return code for the EUPDATESVN command.
> Do we want to drop this one? 

I think we should drop if it is not used.

  reply	other threads:[~2025-05-19 11:36 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-19  7:24 [PATCH v5 0/5] Enable automatic SVN updates for SGX enclaves Elena Reshetova
2025-05-19  7:24 ` [PATCH v5 1/5] x86/sgx: Introduce a counter to count the sgx_(vepc_)open() Elena Reshetova
2025-05-19 10:47   ` Huang, Kai
2025-05-19 11:35     ` Huang, Kai
2025-05-19 11:43       ` Reshetova, Elena
2025-05-19 11:47     ` Reshetova, Elena
2025-05-19 17:28       ` Jarkko Sakkinen
2025-05-19 22:34       ` Huang, Kai
2025-05-20  6:22         ` Reshetova, Elena
2025-05-19 17:21   ` Jarkko Sakkinen
2025-05-20  6:25     ` Reshetova, Elena
2025-05-20 19:55       ` Jarkko Sakkinen
2025-05-19  7:24 ` [PATCH v5 2/5] x86/cpufeatures: Add X86_FEATURE_SGX_EUPDATESVN feature flag Elena Reshetova
2025-05-19  7:47   ` Ingo Molnar
2025-05-19 11:29     ` Reshetova, Elena
2025-05-19 10:53   ` Huang, Kai
2025-05-19 11:29     ` Reshetova, Elena
2025-05-19  7:24 ` [PATCH v5 3/5] x86/sgx: Define error codes for use by ENCLS[EUPDATESVN] Elena Reshetova
2025-05-19 10:57   ` Huang, Kai
2025-05-19 11:30     ` Reshetova, Elena
2025-05-19 11:36       ` Huang, Kai [this message]
2025-05-19  7:24 ` [PATCH v5 4/5] x86/sgx: Implement ENCLS[EUPDATESVN] Elena Reshetova
2025-05-19 11:32   ` Huang, Kai
2025-05-19 11:41     ` Reshetova, Elena
2025-05-19 22:45       ` Huang, Kai
2025-05-20  6:36         ` Reshetova, Elena
2025-05-20 10:42           ` Huang, Kai
2025-05-19 16:02   ` Dave Hansen
2025-05-19 18:24   ` Jarkko Sakkinen
2025-05-20  6:31     ` Reshetova, Elena
2025-05-20 19:57       ` Jarkko Sakkinen
2025-05-20 20:00         ` Dave Hansen
2025-05-19  7:24 ` [PATCH v5 5/5] x86/sgx: Enable automatic SVN updates for SGX enclaves Elena Reshetova
2025-05-19  8:00   ` Ingo Molnar
2025-05-19 11:27     ` Reshetova, Elena
2025-05-19 12:51       ` Ingo Molnar
2025-05-20  6:43         ` Reshetova, Elena
2025-05-20  7:22           ` Ingo Molnar
2025-05-19 18:32   ` Jarkko Sakkinen
2025-05-20  6:46     ` Reshetova, Elena

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=5bdc23827265d1aa53a8e30314dbb049c424c3a9.camel@intel.com \
    --to=kai.huang@intel.com \
    --cc=asit.k.mallick@intel.com \
    --cc=bondarn@google.com \
    --cc=chongc@google.com \
    --cc=dave.hansen@intel.com \
    --cc=dionnaglaze@google.com \
    --cc=elena.reshetova@intel.com \
    --cc=erdemaktas@google.com \
    --cc=jarkko@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sgx@vger.kernel.org \
    --cc=scott.raynor@intel.com \
    --cc=seanjc@google.com \
    --cc=vannapurve@google.com \
    --cc=vincent.r.scarlata@intel.com \
    --cc=x86@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®