Re: [PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

2016-05-09 Thread Jarkko Sakkinen
On Mon, May 09, 2016 at 08:29:17AM +0300, Jarkko Sakkinen wrote: > On Fri, Apr 29, 2016 at 03:22:19PM -0700, Jethro Beekman wrote: > > On 29-04-16 13:04, Jarkko Sakkinen wrote: > > >>> Why would you want to do that? > > >> > > >> ... > > > > > > Do you see this as a performance issue or why do you

Re: [PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

2016-05-08 Thread Jarkko Sakkinen
On Fri, Apr 29, 2016 at 03:22:19PM -0700, Jethro Beekman wrote: > On 29-04-16 13:04, Jarkko Sakkinen wrote: > >>> Why would you want to do that? > >> > >> ... > > > > Do you see this as a performance issue or why do you think that this > > would hurt that much? > > I don't think it's a performance

Re: [PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

2016-04-29 Thread Jethro Beekman
On 29-04-16 13:04, Jarkko Sakkinen wrote: >>> Why would you want to do that? >> >> ... > > Do you see this as a performance issue or why do you think that this > would hurt that much? I don't think it's a performance issue at all. I'm just giving an example of why you'd want to do this. I'm sure p

Re: [PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

2016-04-29 Thread Jarkko Sakkinen
On Wed, Apr 27, 2016 at 04:32:23PM -0700, Jethro Beekman wrote: > On 27-04-16 05:40, Jarkko Sakkinen wrote: > >> The hardware supports calling EEXTEND on only a part of a page, I think the > >> driver should also support that. > > > > Why would you want to do that? > > You might have segments in a

Re: [PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

2016-04-27 Thread Jethro Beekman
On 27-04-16 05:40, Jarkko Sakkinen wrote: >> The hardware supports calling EEXTEND on only a part of a page, I think the >> driver should also support that. > > Why would you want to do that? You might have segments in a binary that don't start at the beginning of a page or that end before the end

Re: [PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

2016-04-27 Thread Jarkko Sakkinen
On Tue, Apr 26, 2016 at 11:49:38PM -0700, Jethro Beekman wrote: > On 25-04-16 10:34, Jarkko Sakkinen wrote: > > diff --git a/drivers/staging/intel_sgx/isgx_ioctl.c > b/drivers/staging/intel_sgx/isgx_ioctl.c > > new file mode 100644 > > index 000..9d8b36b > > --- /dev/null > > +++ b/drivers/stag

Re: [PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

2016-04-26 Thread Jethro Beekman
On 25-04-16 10:34, Jarkko Sakkinen wrote: > diff --git a/drivers/staging/intel_sgx/isgx_ioctl.c b/drivers/staging/intel_sgx/isgx_ioctl.c > new file mode 100644 > index 000..9d8b36b > --- /dev/null > +++ b/drivers/staging/intel_sgx/isgx_ioctl.c > > +static long isgx_ioctl_enclave_create(struct f

Re: [PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

2016-04-25 Thread Jarkko Sakkinen
On Mon, Apr 25, 2016 at 10:55:36AM -0700, Greg KH wrote: > On Mon, Apr 25, 2016 at 08:34:10PM +0300, Jarkko Sakkinen wrote: > > Intel(R) SGX is a set of CPU instructions that can be used by > > applications to set aside private regions of code and data. The code > > outside the enclave is disallow

Re: [PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

2016-04-25 Thread Greg KH
On Mon, Apr 25, 2016 at 08:34:10PM +0300, Jarkko Sakkinen wrote: > Intel(R) SGX is a set of CPU instructions that can be used by > applications to set aside private regions of code and data. The code > outside the enclave is disallowed to access the memory inside the > enclave by the CPU access co

[PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

2016-04-25 Thread Jarkko Sakkinen
Intel(R) SGX is a set of CPU instructions that can be used by applications to set aside private regions of code and data. The code outside the enclave is disallowed to access the memory inside the enclave by the CPU access control. Intel SGX driver provides a ioctl interface for loading and initi