From: Jarkko Sakkinen <jarkko@kernel.org>
To: linux-sgx@vger.kernel.org
Cc: haitao.huang@intel.com, dan.j.williams@intel.com,
dave.hansen@linux.intel.com, bp@alien8.de, tglx@linutronix.de,
linux-kernel@vger.kernel.org, x86@kernel.org,
Jarkko Sakkinen <jarkko@kernel.org>
Subject: [PATCH 0/3] Introduce version array structure: sgx_va
Date: Thu, 25 Feb 2021 00:20:46 +0200 [thread overview]
Message-ID: <20210224222049.240754-1-jarkko@kernel.org> (raw)
Introduce an xarray based version array (VA) structure: struct sgx_va.
The use of sgx_va can be later on extended to the following use cases:
- A global VA for reclaimed SECS pages.
- A global VA for reclaimed VA pages.
Testing done while developing the patch:
- With NUC7PJYH: https://www.intel.com/content/www/us/en/products/boards-kits/nuc/kits/nuc7pjyh.html
- seq 10000 | xargs -I {} -P10000 ./test_sgx > /dev/null
- The EPC size was set from BIOS to 32 MB.
Jarkko Sakkinen (3):
x86/sgx: Move struct sgx_va_page creation to sgx_alloc_va_page()
x86/sgx: Add a version array (VA) structure
x86/sgx: Use sgx_va for the enclave's version array
arch/x86/kernel/cpu/sgx/driver.c | 3 +-
arch/x86/kernel/cpu/sgx/encl.c | 180 ++++++++++++++++++++++---------
arch/x86/kernel/cpu/sgx/encl.h | 36 ++++---
arch/x86/kernel/cpu/sgx/ioctl.c | 77 +++++--------
arch/x86/kernel/cpu/sgx/main.c | 19 +---
5 files changed, 184 insertions(+), 131 deletions(-)
--
2.30.1
next reply other threads:[~2021-02-24 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 22:20 Jarkko Sakkinen [this message]
2021-02-24 22:20 ` [PATCH 1/3] x86/sgx: Move struct sgx_va_page creation to sgx_alloc_va_page() Jarkko Sakkinen
2021-02-24 22:20 ` [PATCH 2/3] x86/sgx: Add a version array (VA) structure Jarkko Sakkinen
2021-02-24 22:20 ` [PATCH 3/3] x86/sgx: Use sgx_va for the enclave's version array Jarkko Sakkinen
2021-02-24 23:48 ` [PATCH 0/3] Introduce version array structure: sgx_va Dave Hansen
2021-02-25 1:01 ` Jarkko Sakkinen
2021-02-25 7:34 ` 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=20210224222049.240754-1-jarkko@kernel.org \
--to=jarkko@kernel.org \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=haitao.huang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--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).