From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: linux-sgx@vger.kernel.org, Andy Lutomirski <luto@kernel.org>
Subject: [PATCH for_v22 v2 0/8] x86/sgx: Remove EADD worker and page copy
Date: Mon, 12 Aug 2019 18:12:44 -0700 [thread overview]
Message-ID: <20190813011252.4121-1-sean.j.christopherson@intel.com> (raw)
As suggested by Andy, remove the work queue in favor of handling the
entire EADD flow in the context of the ioctl(). After the worker is
gone, pass the source page/address directly to EADD instead of first
copying the data into kernel memory.
v2:
- Rebase to master, commit 36e0186296a7.
- Incorporate patch to require EADD be aligned, and add a selftest
update to obey the new alignment requirement.
Sean Christopherson (8):
selftests/x86/sgx: Align enclave binary on 4k boundary
x86/sgx: Require EADD source to be page aligned
x86/sgx: Validate generic SECINFO immediately after copying from user
x86/sgx: Set SGX_ENCL_PAGE_TCS when allocating encl_page
x86/sgx: Move encl_page insertion into tree out of alloc flow
x86/sgx: Allocate encl_page prior to taking encl->lock
x86/sgx: Remove the EADD page worker
x86/sgx: Pass userspace source address directly to EADD
arch/x86/kernel/cpu/sgx/driver/ioctl.c | 405 +++++--------------
arch/x86/kernel/cpu/sgx/driver/main.c | 4 -
arch/x86/kernel/cpu/sgx/encl.h | 2 -
tools/testing/selftests/x86/sgx/encl_piggy.S | 1 +
4 files changed, 106 insertions(+), 306 deletions(-)
--
2.22.0
next reply other threads:[~2019-08-13 1:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 1:12 Sean Christopherson [this message]
2019-08-13 1:12 ` [PATCH for_v22 v2 1/8] selftests/x86/sgx: Align enclave binary on 4k boundary Sean Christopherson
2019-08-16 13:55 ` Jarkko Sakkinen
2019-08-16 15:36 ` Jethro Beekman
2019-08-16 23:41 ` Jarkko Sakkinen
2019-08-13 1:12 ` [PATCH for_v22 v2 2/8] x86/sgx: Require EADD source to be page aligned Sean Christopherson
2019-08-16 14:15 ` Jarkko Sakkinen
2019-08-13 1:12 ` [PATCH for_v22 v2 3/8] x86/sgx: Validate generic SECINFO immediately after copying from user Sean Christopherson
2019-08-13 1:12 ` [PATCH for_v22 v2 4/8] x86/sgx: Set SGX_ENCL_PAGE_TCS when allocating encl_page Sean Christopherson
2019-08-22 12:56 ` Jarkko Sakkinen
2019-08-22 14:24 ` Sean Christopherson
2019-08-13 1:12 ` [PATCH for_v22 v2 5/8] x86/sgx: Move encl_page insertion into tree out of alloc flow Sean Christopherson
2019-08-13 1:12 ` [PATCH for_v22 v2 6/8] x86/sgx: Allocate encl_page prior to taking encl->lock Sean Christopherson
2019-08-13 1:12 ` [PATCH for_v22 v2 7/8] x86/sgx: Remove the EADD page worker Sean Christopherson
2019-08-13 1:12 ` [PATCH for_v22 v2 8/8] x86/sgx: Pass userspace source address directly to EADD Sean Christopherson
2019-08-22 14:37 ` Jarkko Sakkinen
2019-08-22 14:50 ` Sean Christopherson
2019-08-22 17:00 ` Jarkko Sakkinen
2019-08-23 1:25 ` Jarkko Sakkinen
2019-08-23 1:28 ` Sean Christopherson
2019-08-23 1:34 ` Sean Christopherson
2019-08-15 22:00 ` [PATCH for_v22 v2 0/8] x86/sgx: Remove EADD worker and page copy 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=20190813011252.4121-1-sean.j.christopherson@intel.com \
--to=sean.j.christopherson@intel.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-sgx@vger.kernel.org \
--cc=luto@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).