From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Nathaniel McCallum <npmccallum@redhat.com>,
Cedric Xing <cedric.xing@intel.com>,
Jethro Beekman <jethro@fortanix.com>,
Andy Lutomirski <luto@amacapital.net>,
linux-sgx@vger.kernel.org
Subject: Re: [PATCH for_v29 0/8] x86/sgx: Make vDSO callable from C
Date: Sat, 21 Mar 2020 02:55:28 +0200 [thread overview]
Message-ID: <20200321005528.GA7166@linux.intel.com> (raw)
In-Reply-To: <20200320232512.GF3866@linux.intel.com>
On Fri, Mar 20, 2020 at 04:25:12PM -0700, Sean Christopherson wrote:
> On Fri, Mar 20, 2020 at 02:57:24AM +0200, Jarkko Sakkinen wrote:
> > On Wed, Mar 18, 2020 at 06:11:22PM -0700, Sean Christopherson wrote:
> > > Sean Christopherson (8):
> > > x86/sgx: vdso: Remove an incorrect statement the enter enclave comment
> > > x86/sgx: vdso: Make the %rsp fixup on return from handler relative
> > > x86/sgx: vdso: Make __vdso_sgx_enter_enclave() callable from C code
> > > x86/sgx: vdso: Define a typedef for __vdso_sgx_enter_enclave
> > > selftests/x86: sgx: Zero out @result before invoking vDSO sub-test
> > > selftests/x86: sgx: Pass EENTER to vDSO wrapper instead of hardcoding
> > > selftests/x86: sgx: Stop clobbering non-volatile registers
> > > selftests/x86: Add selftest to invoke __vsgx_enter_enclave() from C
> > >
> > > arch/x86/entry/vdso/vsgx_enter_enclave.S | 72 ++-----------------
> > > arch/x86/include/uapi/asm/sgx.h | 61 ++++++++++++++++
> > > .../selftests/x86/sgx/encl_bootstrap.S | 6 +-
> > > tools/testing/selftests/x86/sgx/main.c | 17 ++++-
> > > tools/testing/selftests/x86/sgx/sgx_call.S | 1 -
> > > tools/testing/selftests/x86/sgx/sgx_call.h | 2 +-
> > > 6 files changed, 85 insertions(+), 74 deletions(-)
> > >
> > > --
> > > 2.24.1
> > >
> >
> > Might be a grazy idea but better to go through this anyway.
> >
> > Given the premise that we need the carry the callback anyway in all
> > cases, why won't just have the callback.
> >
> > Why we absolutely need the code path that fills exception info given
> > that we no matter what need to have a callback route?
> >
> > Would simplify considerably to have only clear flow.
>
> Invoking the callback uses a retpoline, which is non-trivial overhead.
> For runtimes that need an assembly wrapper for other reasons, and aren't
> using the untrusted stack, forcing them to implement a handler would be
> painful.
The non-callback route only exists because we did not know that we have
to do the callback route. It does not make sense to add something for
any other reason than absolute necessity.
Things would simplify in the vDSO implementation considerably. Now it is
overwhelmingly complex for no good reason.
/Jarkko
next prev parent reply other threads:[~2020-03-21 0:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 1:11 [PATCH for_v29 0/8] x86/sgx: Make vDSO callable from C Sean Christopherson
2020-03-19 1:11 ` [PATCH for_v29 1/8] x86/sgx: vdso: Remove an incorrect statement the enter enclave comment Sean Christopherson
2020-03-19 20:49 ` Jarkko Sakkinen
2020-03-19 1:11 ` [PATCH for_v29 2/8] x86/sgx: vdso: Make the %rsp fixup on return from handler relative Sean Christopherson
2020-03-20 2:39 ` Jarkko Sakkinen
2020-03-20 2:42 ` Jarkko Sakkinen
2020-03-19 1:11 ` [PATCH for_v29 3/8] x86/sgx: vdso: Make __vdso_sgx_enter_enclave() callable from C code Sean Christopherson
2020-03-19 20:03 ` Xing, Cedric
2020-03-19 20:11 ` Sean Christopherson
2020-03-20 3:07 ` Jarkko Sakkinen
2020-03-20 23:26 ` Sean Christopherson
2020-03-21 0:57 ` Jarkko Sakkinen
2020-03-19 1:11 ` [PATCH for_v29 4/8] x86/sgx: vdso: Define a typedef for __vdso_sgx_enter_enclave Sean Christopherson
2020-03-19 1:11 ` [PATCH for_v29 5/8] selftests/x86: sgx: Zero out @result before invoking vDSO sub-test Sean Christopherson
2020-03-19 1:11 ` [PATCH for_v29 6/8] selftests/x86: sgx: Pass EENTER to vDSO wrapper instead of hardcoding Sean Christopherson
2020-03-19 1:11 ` [PATCH for_v29 7/8] selftests/x86: sgx: Stop clobbering non-volatile registers Sean Christopherson
2020-03-19 1:11 ` [PATCH for_v29 8/8] selftests/x86: Add selftest to invoke __vsgx_enter_enclave() from C Sean Christopherson
2020-03-20 0:57 ` [PATCH for_v29 0/8] x86/sgx: Make vDSO callable " Jarkko Sakkinen
2020-03-20 23:25 ` Sean Christopherson
2020-03-21 0:55 ` Jarkko Sakkinen [this message]
2020-03-21 20:11 ` Sean Christopherson
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=20200321005528.GA7166@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=cedric.xing@intel.com \
--cc=jethro@fortanix.com \
--cc=linux-sgx@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=npmccallum@redhat.com \
--cc=sean.j.christopherson@intel.com \
/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).