[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7533917d-da77-68a5-f1ba-194a1d4a4f68@linux.alibaba.com>
Date: Thu, 11 Feb 2021 14:11:50 +0800
From: Tianjia Zhang <tianjia.zhang@...ux.alibaba.com>
To: Jarkko Sakkinen <jarkko@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>,
Sean Christopherson <seanjc@...gle.com>,
Shuah Khan <shuah@...nel.org>, x86@...nel.org,
linux-sgx@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org,
Jia Zhang <zhang.jia@...ux.alibaba.com>
Subject: Re: [PATCH v4 4/5] x86/sgx: Allows ioctl PROVISION to execute before
CREATE
On 2/3/21 5:57 AM, Jarkko Sakkinen wrote:
> On Mon, Feb 01, 2021 at 09:26:52PM +0800, Tianjia Zhang wrote:
>> In the function sgx_create_enclave(), the direct assignment
>> operation of attributes_mask determines that the ioctl PROVISION
>> operation must be executed after the ioctl CREATE operation,
>> which will limit the flexibility of sgx developers.
>
> Please write acronyms correctly. It's not 'sgx'. It's 'SGX'.
>
> Who are the "sgx developers" and how do they benefit from this?
>
> /Jarkko
>
It mainly refers to application developers based on SGX technology.
One of the benefits that this brings is that the PROVISION operation can
be called before or after the enclave is created, compared to the
previous PROVISION operation can only be executed after the enclave is
created.
Thanks,
Tianjia
Powered by blists - more mailing lists