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>,
	"mingo@kernel.org" <mingo@kernel.org>,
	"Scarlata, Vincent R" <vincent.r.scarlata@intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"jarkko@kernel.org" <jarkko@kernel.org>,
	"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>,
	"Bondarevska, Nataliia" <bondarn@google.com>,
	"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
	"Raynor, Scott" <scott.raynor@intel.com>
Subject: Re: [PATCH v13 4/5] x86/sgx: Implement ENCLS[EUPDATESVN]
Date: Wed, 13 Aug 2025 11:07:33 +0000	[thread overview]
Message-ID: <1a19722b2f979cf34125ec562523ddf0ea8e0b26.camel@intel.com> (raw)
In-Reply-To: <20250813085233.1369036-5-elena.reshetova@intel.com>


>  
> +/* Counter to count the active SGX users */
> +static int sgx_usage_count;
> 

[...]

> + * Return:
> + * %0:			- Success or not supported
> + * %-EAGAIN:	- Can be safely retried, failure is due to lack of
> + *				entropy in RNG
> + * %-EIO:		- Unexpected error, retries are not advisable
> + */

This time I actually downloaded those patches and applied to my local, and
I found the descriptions of the error codes are not vertically aligned.

Please fix (and it's sad we still need to fix this type of thing in v13).

Nit: as said before, the k-doc comment doc says:

    .. in order to produce the desired line breaks, you need to use a ReST
    list, e. g.:

    * Return:
    * * %0            - OK to runtime suspend the device
    * * %-EBUSY       - Device should not be runtime suspended

(hint: there's an additional '*' before the '%'.)

But I guess it's just a nit but not a blocker.

> +static int __maybe_unused sgx_update_svn(void)
> +{
> +	int ret;
> +
> +	/*
> +	 * If EUPDATESVN is not available, it is ok to
> +	 * silently skip it to comply with legacy behavior.
> +	 */
> +	if (!cpu_feature_enabled(X86_FEATURE_SGX_EUPDATESVN))
> +		return 0;
> +
> +	/*
> +	 * EPC is guaranteed to be empty when there are no users.
> +	 * Ensure we are on our first user before proceeding further.
> +	 */
> +	WARN(sgx_usage_count != 1, "Elevated usage count when calling EUPDATESVN\n");

It seems you are obsessed to use "!= 1", rather than "!= 0".

IIUC, Dave suggested the latter [*]:

    	/* EPC is guaranteed to be empty when there are no users: */
	WARN(count, "Elevated usage count...");

.. which is my natural response too.

And the odd is I actually need to look at the next patch to see why "!= 1"
is used.

[*]
https://lore.kernel.org/linux-sgx/20250801112619.1117549-1-elena.reshetova@intel.com/T/#m2225b27448de868a7bc1b86ed7f2ee784367ba84

  reply	other threads:[~2025-08-13 11:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-13  8:50 [PATCH v13 0/5] Enable automatic SVN updates for SGX enclaves Elena Reshetova
2025-08-13  8:50 ` [PATCH v13 1/5] x86/sgx: Introduce functions to count the sgx_(vepc_)open() Elena Reshetova
2025-08-13  8:50 ` [PATCH v13 2/5] x86/cpufeatures: Add X86_FEATURE_SGX_EUPDATESVN feature flag Elena Reshetova
2025-08-13  8:50 ` [PATCH v13 3/5] x86/sgx: Define error codes for use by ENCLS[EUPDATESVN] Elena Reshetova
2025-08-13  8:50 ` [PATCH v13 4/5] x86/sgx: Implement ENCLS[EUPDATESVN] Elena Reshetova
2025-08-13 11:07   ` Huang, Kai [this message]
2025-08-13 13:56     ` Reshetova, Elena
2025-08-13  8:50 ` [PATCH v13 5/5] x86/sgx: Enable automatic SVN updates for SGX enclaves Elena Reshetova
2025-08-13 11:07   ` Huang, Kai
2025-08-13 13:53     ` 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=1a19722b2f979cf34125ec562523ddf0ea8e0b26.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=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=mingo@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®