From: Jarkko Sakkinen <jarkko@kernel.org>
To: Reinette Chatre <reinette.chatre@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-sgx@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v5 2/2] x86/sgx: Add an attribute for the amount of SGX memory in a NUMA node
Date: Thu, 23 Sep 2021 23:30:14 +0300 [thread overview]
Message-ID: <254864594af4cde213a37a4db527e293a1ef1d7a.camel@kernel.org> (raw)
In-Reply-To: <f45245ba-41b8-62ae-38b5-64725a214bad@intel.com>
On Wed, 2021-09-22 at 16:30 -0700, Reinette Chatre wrote:
> Hi Jarkko,
>
> On 9/13/2021 8:04 PM, Jarkko Sakkinen wrote:
> > The amount of SGX memory on the system is determined by the BIOS and it
> > varies wildly between systems. It can be from dozens of MB's on desktops
> > or VM's, up to many GB's on servers. Just like for regular memory, it is
> > sometimes useful to know the amount of usable SGX memory in the system.
> >
> > Add an attribute for the amount of SGX memory in bytes to each NUMA
> > node. The path is /sys/devices/system/node/node[0-9]*/sgx/memory_size.
> >
> > Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
> >
> > ---
> > v5: A new patch based on the discussion at
> > https://lore.kernel.org/linux-sgx/3a7cab4115b4f902f3509ad8652e616b91703e1d.camel@kernel.org/T/#t
> > ---
> > Documentation/x86/sgx.rst | 14 ++++++
> > arch/x86/kernel/cpu/sgx/main.c | 90 ++++++++++++++++++++++++++++++++++
> > arch/x86/kernel/cpu/sgx/sgx.h | 2 +
> > 3 files changed, 106 insertions(+)
> >
>
> ...
>
> > diff --git a/arch/x86/kernel/cpu/sgx/main.c b/arch/x86/kernel/cpu/sgx/main.c
> > index a6e313f1a82d..c43b5a0120c1 100644
> > --- a/arch/x86/kernel/cpu/sgx/main.c
> > +++ b/arch/x86/kernel/cpu/sgx/main.c
> > @@ -717,6 +717,7 @@ static bool __init sgx_page_cache_init(void)
> > }
> >
> > sgx_epc_sections[i].node = &sgx_numa_nodes[nid];
> > + sgx_numa_nodes[nid].size += size;
> >
> > sgx_nr_epc_sections++;
> > }
>
> The above memory seems to be uninitialized at the time it is incremented.
>
> I tried this out on a system that reports the following:
>
> $ dmesg | grep EPC
> [ 7.252838] sgx: EPC section 0x1000c00000-0x107f7fffff
> [ 7.256921] sgx: EPC section 0x2000c00000-0x207fffffff
>
> It shows unexpectedly large values:
> $ cat /sys/devices/system/node/node*/sgx/memory_size
> 12421486739271732874
> 16308428754864105707
>
> System reported sane values after adding this fixup:
>
> diff --git a/arch/x86/kernel/cpu/sgx/main.c b/arch/x86/kernel/cpu/sgx/main.c
> index 3380390cc052..d73bbfbfc05d 100644
> --- a/arch/x86/kernel/cpu/sgx/main.c
> +++ b/arch/x86/kernel/cpu/sgx/main.c
> @@ -621,7 +621,7 @@ static bool __init sgx_page_cache_init(void)
> int nid;
> int i;
>
> - sgx_numa_nodes = kmalloc_array(num_possible_nodes(),
> sizeof(*sgx_numa_nodes), GFP_KERNEL);
> + sgx_numa_nodes = kcalloc(num_possible_nodes(),
> sizeof(*sgx_numa_nodes), GFP_KERNEL);
> if (!sgx_numa_nodes)
> return false;
>
>
> After fixup:
> $ cat /sys/devices/system/node/node*/sgx/memory_size
> 2126512128
> 2134900736
Thanks! I did not experience in a VM.
So cat you pick these patches to your patch set, and squash
this fix to it?
/Jarkko
next prev parent reply other threads:[~2021-09-23 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210914030422.377601-1-jarkko@kernel.org>
2021-09-14 3:04 ` [PATCH v5 2/2] x86/sgx: Add an attribute for the amount of SGX memory in a NUMA node Jarkko Sakkinen
2021-09-22 23:30 ` Reinette Chatre
2021-09-23 20:30 ` Jarkko Sakkinen [this message]
2021-09-23 20:39 ` Reinette Chatre
2021-09-28 3:01 ` 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=254864594af4cde213a37a4db527e293a1ef1d7a.camel@kernel.org \
--to=jarkko@kernel.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).