[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <154ded23-fd1d-f324-4e0a-9de8eddcda6d@intel.com>
Date: Mon, 5 Nov 2018 12:27:11 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>, x86@...nel.org,
platform-driver-x86@...r.kernel.org, linux-sgx@...r.kernel.org
Cc: sean.j.christopherson@...el.com, nhorman@...hat.com,
npmccallum@...hat.com, serge.ayoun@...el.com,
shay.katz-zamir@...el.com, haitao.huang@...el.com,
mark.shanahan@...el.com, andriy.shevchenko@...ux.intel.com,
Jonathan Corbet <corbet@....net>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v15 23/23] x86/sgx: Driver documentation
On 11/2/18 4:11 PM, Jarkko Sakkinen wrote:
> Documentation/index.rst | 1 +
> Documentation/x86/intel_sgx.rst | 185 ++++++++++++++++++++++++++++++++
> 2 files changed, 186 insertions(+)
> create mode 100644 Documentation/x86/intel_sgx.rst
This patch set establishes an ABI. It basically sets in stone a bunch
of behaviors that the enclave, the kernel, and the out-of-enclave code
must follow.
There are a bunch of things that the enclave can do to %rsp or %rip, for
instance, that it is capable and/or permitted to do.
The ABI seems entirely undocumented and rather lightly designed, which
seems like something we should fix before this is merged.
Also, for a feature as massive and complicated as this one, it seems
irresponsible to not have a selftest. Is that not feasible for some reason?
Powered by blists - more mailing lists