From: Jethro Beekman <jethro@fortanix.com>
To: Dave Hansen <dave.hansen@intel.com>,
Raoul Strackx <raoul.strackx@fortanix.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-sgx@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] x86/sgx: eextend ioctl
Date: Mon, 12 Apr 2021 19:01:39 +0200 [thread overview]
Message-ID: <4e478984-e692-3b6a-771b-8eb73f6d82a7@fortanix.com> (raw)
In-Reply-To: <1c8f5c58-6cea-7f43-81ed-fa165af2b59d@intel.com>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
On 2021-04-12 18:47, Dave Hansen wrote:
> On 4/12/21 9:41 AM, Jethro Beekman wrote:
>> Yes this still doesn't let one execute all possible ECREATE, EADD, EEXTEND, EINIT sequences.
>
> OK, so we're going in circles now.
>
> I don't believe we necessarily *WANT* or need Linux to support "all
> possible ECREATE, EADD, EEXTEND, EINIT sequences". Yet, it's what is
> being used to justify this series without any other justification.
>
> It's going to be a different story if you bring me a real enclave that
> *REALLY* wants to do this for good reasons.
>
It's still not clear to me what your motivations are for trying to keep Linux incompatible with the rest of the world.
--
Jethro Beekman | Fortanix
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4490 bytes --]
next prev parent reply other threads:[~2021-04-12 17:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 8:59 [PATCH v2 0/3] x86/sgx: eextend ioctl Raoul Strackx
2021-04-12 9:04 ` [PATCH v2 1/3] x86/sgx: Adding " Raoul Strackx
2021-04-12 9:04 ` [PATCH v2 2/3] x86/sgx: Fix compatibility issue with OPENSSL < 1.1.0 Raoul Strackx
2021-04-12 9:05 ` [PATCH v2 3/3] x86/sgx: eextend ioctl selftest Raoul Strackx
2021-04-12 15:36 ` [PATCH v2 0/3] x86/sgx: eextend ioctl Dave Hansen
2021-04-12 15:58 ` Jethro Beekman
2021-04-12 16:40 ` Dave Hansen
2021-04-12 16:41 ` Jethro Beekman
2021-04-12 16:47 ` Dave Hansen
2021-04-12 17:01 ` Jethro Beekman [this message]
2021-04-14 11:07 ` Jarkko Sakkinen
2021-04-14 10:52 ` Jarkko Sakkinen
2021-04-14 11:01 ` Jethro Beekman
2021-04-16 13:08 ` Jarkko Sakkinen
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=4e478984-e692-3b6a-771b-8eb73f6d82a7@fortanix.com \
--to=jethro@fortanix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=raoul.strackx@fortanix.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