public inbox for linux-sgx@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Aaron Lu" <aaron.lu@intel.com>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	"Kai Huang" <kai.huang@intel.com>
Cc: "Molina Sabido, Gerardo" <gerardo.molina.sabido@intel.com>,
	"Zhimin Luo" <zhimin.luo@intel.com>, <linux-sgx@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <x86@kernel.org>
Subject: Re: [PATCH v2 1/2] x86/sgx: Fix deadlock in SGX NUMA node search
Date: Thu, 05 Sep 2024 17:21:54 +0300	[thread overview]
Message-ID: <D3YF1PO93RI0.2V31UQ4D620TT@kernel.org> (raw)
In-Reply-To: <20240905080855.1699814-2-aaron.lu@intel.com>

On Thu Sep 5, 2024 at 11:08 AM EEST, Aaron Lu wrote:
> When the current node doesn't have an EPC section configured by firmware
> and all other EPC sections are used up, CPU can get stuck inside the
> while loop that looks for an available EPC page from remote nodes
> indefinitely, leading to a soft lockup. Note how nid_of_current will
> never be equal to nid in that while loop because nid_of_current is not
> set in sgx_numa_mask.
>
> Also worth mentioning is that it's perfectly fine for the firmware not
> to setup an EPC section on a node. While setting up an EPC section on
> each node can enhance performance, it is not a requirement for
> functionality.
>
> Rework the loop to start and end on *a* node that has SGX memory. This
> avoids the deadlock looking for the current SGX-lacking node to show up
> in the loop when it never will.
>
> Fixes: 901ddbb9ecf5 ("x86/sgx: Add a basic NUMA allocation scheme to sgx_alloc_epc_page()")
> Reported-by: "Molina Sabido, Gerardo" <gerardo.molina.sabido@intel.com>
> Tested-by: Zhimin Luo <zhimin.luo@intel.com>
> Reviewed-by: Kai Huang <kai.huang@intel.com>
> Acked-by: Dave Hansen <dave.hansen@linux.intel.com>
> Signed-off-by: Aaron Lu <aaron.lu@intel.com>
> ---
>  arch/x86/kernel/cpu/sgx/main.c | 27 ++++++++++++++-------------
>  1 file changed, 14 insertions(+), 13 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/sgx/main.c b/arch/x86/kernel/cpu/sgx/main.c
> index 1a000acd933a..694fcf7a5e3a 100644
> --- a/arch/x86/kernel/cpu/sgx/main.c
> +++ b/arch/x86/kernel/cpu/sgx/main.c
> @@ -475,24 +475,25 @@ struct sgx_epc_page *__sgx_alloc_epc_page(void)
>  {
>  	struct sgx_epc_page *page;
>  	int nid_of_current = numa_node_id();
> -	int nid = nid_of_current;
> +	int nid_start, nid;
>  
> -	if (node_isset(nid_of_current, sgx_numa_mask)) {
> -		page = __sgx_alloc_epc_page_from_node(nid_of_current);
> -		if (page)
> -			return page;
> -	}
> -
> -	/* Fall back to the non-local NUMA nodes: */
> -	while (true) {
> -		nid = next_node_in(nid, sgx_numa_mask);
> -		if (nid == nid_of_current)
> -			break;
> +	/*
> +	 * Try local node first. If it doesn't have an EPC section,
> +	 * fall back to the non-local NUMA nodes.
> +	 */
> +	if (node_isset(nid_of_current, sgx_numa_mask))
> +		nid_start = nid_of_current;
> +	else
> +		nid_start = next_node_in(nid_of_current, sgx_numa_mask);
>  
> +	nid = nid_start;
> +	do {
>  		page = __sgx_alloc_epc_page_from_node(nid);
>  		if (page)
>  			return page;
> -	}
> +
> +		nid = next_node_in(nid, sgx_numa_mask);
> +	} while (nid != nid_start);
>  
>  	return ERR_PTR(-ENOMEM);
>  }

Looks good to me:

Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>

BR, Jarkko

  reply	other threads:[~2024-09-05 14:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05  8:08 [PATCH v2 0/2] SGX NUMA fix Aaron Lu
2024-09-05  8:08 ` [PATCH v2 1/2] x86/sgx: Fix deadlock in SGX NUMA node search Aaron Lu
2024-09-05 14:21   ` Jarkko Sakkinen [this message]
2024-09-05  8:08 ` [PATCH v2 2/2] x86/sgx: Log information when a node lacks an EPC section Aaron Lu
2024-09-05 14:24   ` Jarkko Sakkinen
2024-09-05 19:02     ` Dave Hansen
2024-09-05 22:16   ` Huang, Kai

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=D3YF1PO93RI0.2V31UQ4D620TT@kernel.org \
    --to=jarkko@kernel.org \
    --cc=aaron.lu@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=gerardo.molina.sabido@intel.com \
    --cc=kai.huang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sgx@vger.kernel.org \
    --cc=x86@kernel.org \
    --cc=zhimin.luo@intel.com \
    /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