From: Dave Hansen <dave.hansen@intel.com>
To: Jarkko Sakkinen <jarkko@kernel.org>, linux-sgx@vger.kernel.org
Cc: Reinette Chatre <reinette.chatre@intel.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH RFC v3] x86/sgx: Add /proc/sys/kernel/sgx/total_mem
Date: Wed, 11 Aug 2021 07:30:13 -0700 [thread overview]
Message-ID: <0c935066-008d-b023-7dc3-f4e0ac1b3d20@intel.com> (raw)
In-Reply-To: <20210811032133.853680-1-jarkko@kernel.org>
On 8/10/21 8:21 PM, Jarkko Sakkinen wrote:
> +The following sysctl files can be found in the ``/proc/sys/kernel/sgx/`` directory:
> +
> +``total_mem``
> + The total amount of SGX protected memory in bytes available in the system
> + available for use. In other words, it describes the size of the Enclave
> + Page Cache (EPC).
I've been acting as if /proc is deprecated for new stuff. Shouldn't
this be going in sysfs?
I figured, at some point, someone is going to ask for NUMA statistics.
That would tend to point in the direction of us needing something in:
/sys/devices/system/node/nodeN/
Maybe 'sgxinfo' or 'sgxstat' to go along with 'meminfo'.
But, we'll probably also end up needing some stats for other things.
Folks have, for instance, asked for a counter of the number of
instantiated enclaves.
We could also use the drivers' namespaces:
/sys/class/misc/sgx_enclave
/sys/class/misc/sgx_provision
/sys/class/misc/sgx_vepc
although that is a bit awkward for reporting global resources like memory.
We could create a platform device just for these stats, say:
/sys/bus/platform/devices/sgx
But I think platform devices are rather highly scrutinized these days.
I'm not sure if SGX counts as one.
/sys/kernel also appears to be a bit of a free-for-all. Perhaps it
could go in:
/sys/kernel/sgx
or
/sys/kernel/enclaves
The other crazy thing we could try would be to just hijack core mm
mechanisms:
/proc/{meminfo,vmstat}
/sys/devices/system/node/nodeN/{vmstat,meminfo}
Then we can just use the existing counter infrastructure, which I think
gets us into /sys and /proc. I'm not sure the mm folks would be fond of
this for something arch and vendor specific, though.
In any case, ABIs are hard and SGX is weird. News at 11.
next prev parent reply other threads:[~2021-08-11 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 3:21 Jarkko Sakkinen
2021-08-11 14:30 ` Dave Hansen [this message]
2021-08-12 19:53 ` Jarkko Sakkinen
2021-08-12 20:04 ` Dave Hansen
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=0c935066-008d-b023-7dc3-f4e0ac1b3d20@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--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
all inboxes | Powered by JetHome®