From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
X86 ML <x86@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Josh Triplett <josh@joshtriplett.org>,
linux-sgx@vger.kernel.org, haitao.huang@linux.intel.com,
Jethro Beekman <jethro@fortanix.com>,
"Dr. Greg Wettstein" <greg@enjellic.com>
Subject: Re: [RFC PATCH v2 4/4] x86/vdso: Add __vdso_sgx_enter_enclave() to wrap SGX enclave transitions
Date: Fri, 7 Dec 2018 12:35:57 -0800 [thread overview]
Message-ID: <20181207203557.GF10404@linux.intel.com> (raw)
In-Reply-To: <4CEB5945-9562-40FA-8CCA-A1675D55B001@amacapital.net>
On Fri, Dec 07, 2018 at 12:16:59PM -0800, Andy Lutomirski wrote:
>
> > On Dec 7, 2018, at 12:09 PM, Sean Christopherson <sean.j.christopherson@intel.com> wrote:
> >
> > Speaking of preserving registers, the asm blob needs to mark RBX as
> > clobbered since it's modified for EEXIT.
>
> Have fun with that. The x86_32 compiler seems to really like having its
> PIC register preserved, and you may get some lovely compiler errors.
Tagentinally related, as-is the SGX vDSO is only compiled for x86_64
since CONFIG_SGX depends on CONFIG_X86_64. Mapping the EPC in 32-bit
mode complicates things and no one is asking for SGX support on 32-bit
builds, so...
next prev parent reply other threads:[~2018-12-07 20:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 22:19 [RFC PATCH v2 0/4] x86: Add vDSO exception fixup for SGX Sean Christopherson
2018-12-06 22:19 ` [RFC PATCH v2 1/4] x86/vdso: Add support for exception fixup in vDSO functions Sean Christopherson
2018-12-06 22:19 ` [RFC PATCH v2 2/4] x86/fault: Attempt to fixup unhandled #PF in vDSO before signaling Sean Christopherson
2018-12-06 22:19 ` [RFC PATCH v2 3/4] x86/traps: Attempt to fixup exceptions " Sean Christopherson
2018-12-06 22:19 ` [RFC PATCH v2 4/4] x86/vdso: Add __vdso_sgx_enter_enclave() to wrap SGX enclave transitions Sean Christopherson
2018-12-06 22:50 ` Andy Lutomirski
2018-12-07 16:51 ` Sean Christopherson
2018-12-07 17:56 ` Andy Lutomirski
2018-12-07 19:02 ` Sean Christopherson
2018-12-07 19:23 ` Andy Lutomirski
2018-12-07 20:09 ` Sean Christopherson
2018-12-07 20:16 ` Andy Lutomirski
2018-12-07 20:35 ` Sean Christopherson [this message]
2018-12-07 21:26 ` Sean Christopherson
2018-12-07 23:33 ` Andy Lutomirski
2018-12-11 19:31 ` Sean Christopherson
2018-12-11 20:04 ` Andy Lutomirski
2018-12-11 22:00 ` Sean Christopherson
2018-12-11 23:12 ` Andy Lutomirski
2018-12-07 16:31 ` Dr. Greg
2018-12-07 18:05 ` Andy Lutomirski
2018-12-07 18:19 ` Jethro Beekman
2018-12-07 18:15 ` Jethro Beekman
2018-12-07 18:44 ` Dave Hansen
2018-12-07 18:50 ` Andy Lutomirski
2018-12-08 8:15 ` Jethro Beekman
2018-12-14 15:04 ` 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=20181207203557.GF10404@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=greg@enjellic.com \
--cc=haitao.huang@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jethro@fortanix.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.