From: Jarkko Sakkinen <jarkko@kernel.org>
To: Jethro Beekman <jethro@fortanix.com>
Cc: Dave Hansen <dave.hansen@intel.com>,
Raoul Strackx <raoul.strackx@fortanix.com>,
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 RESEND 0/3] x86/sgx: eextend ioctl
Date: Sun, 4 Apr 2021 19:04:18 +0300 [thread overview]
Message-ID: <YGnjgkAQjiS8QcS7@kernel.org> (raw)
In-Reply-To: <9a841584-65e8-31e9-6bd4-0140b33434e8@fortanix.com>
On Fri, Apr 02, 2021 at 08:31:19PM +0200, Jethro Beekman wrote:
> On 2021-04-02 17:53, Dave Hansen wrote:
> > On 4/2/21 1:38 AM, Jethro Beekman wrote:
> >>> So, we're talking here about pages that have been EEADDED, but for
> >>> which we do not want to include the entire contents of the page?
> >>> Do these contents always include the beginning of the page, or can
> >>> the holes be anywhere?
> >> Holes can be anywhere, and EEXTEND calls need not be sequential in
> >> memory address or even relate to the most recently EADDed page.
> >
> > I think you're referring to the SGX architecture itself here. The
> > architecture permits this, right?
>
> Yes.
>
> > But, why would an enclave loader application ever do this?
>
> e.g. to save space
>
> > Is this something we want to support in Linux?
>
> Why not? Is there a good reason to not fully support this part of the CPU architecture?
Yes, in generic sense :-)
If one would disagree, that would be same as saying that everything should
execute in ring-0 because that only gives "full support".
/Jarkko
next prev parent reply other threads:[~2021-04-04 16:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 12:50 [PATCH RESEND 0/3] x86/sgx: eextend ioctl Raoul Strackx
2021-03-31 15:53 ` Dave Hansen
2021-04-01 14:56 ` Raoul Strackx
2021-04-01 16:11 ` Dave Hansen
2021-04-01 17:49 ` Raoul Strackx
2021-04-01 18:40 ` Dave Hansen
2021-04-02 8:38 ` Jethro Beekman
2021-04-02 15:53 ` Dave Hansen
2021-04-02 18:31 ` Jethro Beekman
2021-04-02 18:42 ` Dave Hansen
2021-04-02 19:38 ` Jethro Beekman
2021-04-02 19:50 ` Dave Hansen
2021-04-02 20:20 ` Jethro Beekman
2021-04-02 20:48 ` Dave Hansen
2021-04-08 15:27 ` Jethro Beekman
2021-04-08 15:54 ` Dave Hansen
2021-04-04 16:04 ` Jarkko Sakkinen [this message]
2021-04-08 15:07 ` Jethro Beekman
2021-04-01 17:59 ` Jethro Beekman
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=YGnjgkAQjiS8QcS7@kernel.org \
--to=jarkko@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jethro@fortanix.com \
--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