public inbox for linux-sgx@vger.kernel.org
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: Jarkko Sakkinen <jarkko@kernel.org>,
	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: [PATCH v2 0/2] SGX NUMA fix
Date: Thu,  5 Sep 2024 16:08:53 +0800	[thread overview]
Message-ID: <20240905080855.1699814-1-aaron.lu@intel.com> (raw)

Hi,

A soft lockup issue was found during some SGX testing and it turned
out to be a problem in SGX code related to NUMA, please see patch1/2
for details.

While Dave reviewed v1 of patch1/2, he suggested dumping an info when
a node has both CPUs and memory but no EPC section, so that's patch2/2.

Comments are welcome, thanks.

v2:
- Enhance changelog for patch1/2 according to Kai, Dave and Jarkko's
  suggestions;
- Fix Reported-by tag, it should be Gerardo. Sorry for the mistake.
- Collect review tags.
- Add patch2/2.

Aaron Lu (2):
  x86/sgx: Fix deadlock in SGX NUMA node search
  x86/sgx: Log information when a node lacks an EPC section

 arch/x86/kernel/cpu/sgx/main.c | 34 +++++++++++++++++++++-------------
 1 file changed, 21 insertions(+), 13 deletions(-)

-- 
2.45.2


             reply	other threads:[~2024-09-05  8:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05  8:08 Aaron Lu [this message]
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
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=20240905080855.1699814-1-aaron.lu@intel.com \
    --to=aaron.lu@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=gerardo.molina.sabido@intel.com \
    --cc=jarkko@kernel.org \
    --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