From: Dave Hansen <dave.hansen@intel.com>
To: Nathan Chancellor <nathan@kernel.org>,
Jarkko Sakkinen <jarkko@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
reinette.chatre@intel.com, linux-kernel@vger.kernel.org,
linux-sgx@vger.kernel.org
Subject: Re: [PATCH v13 2/2] x86/sgx: Add an attribute for the amount of SGX memory in a NUMA node
Date: Fri, 17 Dec 2021 13:17:42 -0800 [thread overview]
Message-ID: <b744d47e-4b7f-d372-f8ba-758555c08993@intel.com> (raw)
In-Reply-To: <YbzhBrimHGGpddDM@archlinux-ax161>
On 12/17/21 11:12 AM, Nathan Chancellor wrote:
> With this patch in -next as commit 50468e431335 ("x86/sgx: Add an
> attribute for the amount of SGX memory in a NUMA node"), this sysfs node
> causes an OOPS for me on at least one of my test systems (Intel based):
Thanks for the report!
Could you share /proc/cpuinfo and a full dmesg from when this happens?
I'm curious if your system has SGX at all and if it had any issues
during initialization.
next prev parent reply other threads:[~2021-12-17 21:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 16:21 [PATCH v13 1/2] x86/sgx: Rename fallback labels in sgx_init() Jarkko Sakkinen
2021-11-16 16:21 ` [PATCH v13 2/2] x86/sgx: Add an attribute for the amount of SGX memory in a NUMA node Jarkko Sakkinen
2021-12-04 23:51 ` Jarkko Sakkinen
2021-12-07 19:36 ` Dave Hansen
2021-12-08 10:10 ` Borislav Petkov
2021-12-08 19:38 ` Dave Hansen
2021-12-09 12:08 ` Borislav Petkov
2021-12-11 15:37 ` Jarkko Sakkinen
2021-12-11 15:36 ` Jarkko Sakkinen
2021-12-09 15:35 ` [tip: x86/sgx] " tip-bot2 for Jarkko Sakkinen
2021-12-17 19:12 ` [PATCH v13 2/2] " Nathan Chancellor
2021-12-17 21:17 ` Dave Hansen [this message]
2021-12-17 22:04 ` Nathan Chancellor
2021-12-28 23:45 ` Jarkko Sakkinen
2022-01-02 4:54 ` Dave Hansen
2022-01-02 23:20 ` Nathan Chancellor
2022-01-04 16:52 ` Dave Hansen
2022-01-06 19:18 ` Jarkko Sakkinen
2022-01-07 11:42 ` Jarkko Sakkinen
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=b744d47e-4b7f-d372-f8ba-758555c08993@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=rafael@kernel.org \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--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®