From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: x86@kernel.org, platform-driver-x86@vger.kernel.org,
linux-sgx@vger.kernel.org, dave.hansen@intel.com,
nhorman@redhat.com, npmccallum@redhat.com, serge.ayoun@intel.com,
shay.katz-zamir@intel.com, haitao.huang@intel.com,
andriy.shevchenko@linux.intel.com, tglx@linutronix.de,
kai.svahn@intel.com, Shuah Khan <shuah@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Andy Lutomirski <luto@kernel.org>,
Dmitry Safonov <dima@arista.com>,
Florian Weimer <fweimer@redhat.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Suresh Siddha <suresh.b.siddha@intel.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH RFC] selftests/x86: Add a selftest for SGX
Date: Thu, 15 Nov 2018 22:37:44 +0200 [thread overview]
Message-ID: <20181115203744.GD26875@linux.intel.com> (raw)
In-Reply-To: <20181114160941.GA1387@linux.intel.com>
On Wed, Nov 14, 2018 at 08:09:42AM -0800, Sean Christopherson wrote:
> On Tue, Nov 13, 2018 at 11:40:09PM +0200, Jarkko Sakkinen wrote:
> > Add a selftest for SGX. It is a trivial test where a simple enclave
> > copies one 64-bit word of memory between two memory locations given to
> > the enclave as arguments.
> >
> > Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> > ---
> > +SUBDIRS_64 := sgx
> > +ASSERT(!DEFINED(.altinstructions), "ALTERNATIVES are not supported in the SGX LE")
> > +ASSERT(!DEFINED(.altinstr_replacement), "ALTERNATIVES are not supported in the SGX LE")
> > +ASSERT(!DEFINED(.discard.retpoline_safe), "RETPOLINE ALTERNATIVES are not supported in the SGX LE")
> > +ASSERT(!DEFINED(.discard.nospec), "RETPOLINE ALTERNATIVES are not supported in the SGX LE")
>
> Maybe this?
>
> s/LE/Test Enclave
Sure.
> > diff --git a/tools/testing/selftests/x86/sgx/encl_bootstrap.S b/tools/testing/selftests/x86/sgx/encl_bootstrap.S
> > new file mode 100644
> > index 000000000000..62251c7d9927
> > --- /dev/null
> > +++ b/tools/testing/selftests/x86/sgx/encl_bootstrap.S
> > @@ -0,0 +1,94 @@
> > +/* SPDX-License-Identifier: (GPL-2.0 OR BSD-3-Clause) */
> > +/*
> > + * Copyright(c) 2016-18 Intel Corporation.
> > + */
> > +
> > + .macro ENCLU
> > + .byte 0x0f, 0x01, 0xd7
> > + .endm
> > +
> > + .section ".tcs", "a"
> > + .balign 4096
> > +
> > + .fill 1, 8, 0 # STATE (set by CPU)
> > + .fill 1, 8, 0 # FLAGS
> > + .long encl_ssa # OSSA
>
> Any reason not to do .quad for OSSA and OENTRY?
Probably not.
> > + .fill 1, 4, 0
> > + .fill 1, 4, 0 # CSSA (set by CPU)
> > + .fill 1, 4, 1 # NSSA
> > + .long encl_entry # OENTRY
> > + .fill 1, 4, 0
> > + .fill 1, 8, 0 # AEP (set by EENTER and ERESUME)
> > + .fill 1, 8, 0 # OFSBASE
> > + .fill 1, 8, 0 # OGSBASE
> > + .fill 1, 4, 0xFFFFFFFF # FSLIMIT
> > + .fill 1, 4, 0xFFFFFFFF # GSLIMIT
> > + .fill 503, 8, 0 # Reserved
>
> I'd prefer to do 1-byte fill with a size of 4024 to match the SDM.
Sure.
> > +
> > + .text
> > +
> > +encl_entry:
> > + # %rbx contains the base address for TCS, which is also the first
> > + # address inside the enclave. By adding $le_stack_end to it, we get the
> > + # absolute address for the stack.
> > + lea (encl_stack)(%rbx), %rax
> > + xchg %rsp, %rax
> > + push %rax
> > +
> > + push %rcx # push the address after EENTER
> > + push %rbx # push the enclave base address
> > +
> > + call encl_body
> > +
> > + pop %rbx # pop the enclave base address
> > +
> > + # Restore XSAVE registers to a synthetic state.
> > + mov $0xFFFFFFFF, %rax
> > + mov $0xFFFFFFFF, %rdx
> > + lea (xsave_area)(%rbx), %rdi
> > + fxrstor (%rdi)
> > +
> > + # Clear GPRs
> > + xor %rcx, %rcx
> > + xor %rdx, %rdx
> > + xor %rdi, %rdi
> > + xor %rsi, %rsi
> > + xor %r8, %r8
> > + xor %r9, %r9
> > + xor %r10, %r10
> > + xor %r11, %r11
> > + xor %r12, %r12
> > + xor %r13, %r13
> > + xor %r14, %r14
> > + xor %r15, %r15
> > +
> > + # Reset status flags
> > + add %rdx, %rdx # OF = SF = AF = CF = 0; ZF = PF = 1
> > +
> > + pop %rbx # pop the address after EENTER
>
> Probably worth expanding the comment to explain that ENCLU[EEXIT] takes the
> target address via %rbx, i.e. we're "returning" from the EENTER "call".
Thank you for the feedback. I'll do all of these updates.
/Jarkko
prev parent reply other threads:[~2018-11-15 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 21:40 [PATCH RFC] selftests/x86: Add a selftest for SGX Jarkko Sakkinen
2018-11-13 21:51 ` Dave Hansen
2018-11-15 20:33 ` Jarkko Sakkinen
2018-11-14 16:09 ` Sean Christopherson
2018-11-15 20:37 ` Jarkko Sakkinen [this message]
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=20181115203744.GD26875@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dave.hansen@intel.com \
--cc=dima@arista.com \
--cc=fweimer@redhat.com \
--cc=haitao.huang@intel.com \
--cc=kai.svahn@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=nhorman@redhat.com \
--cc=npmccallum@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=serge.ayoun@intel.com \
--cc=shay.katz-zamir@intel.com \
--cc=shuah@kernel.org \
--cc=suresh.b.siddha@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