From: Jarkko Sakkinen <jarkko@kernel.org>
To: "Zhang, Cathy" <cathy.zhang@intel.com>
Cc: "linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"Raj, Ashok" <ashok.raj@intel.com>
Subject: Re: [RFC PATCH v3 03/10] x86/sgx: Save enclave pointer for VA page
Date: Wed, 06 Apr 2022 09:33:11 +0300 [thread overview]
Message-ID: <e16bfc917ac85da8e2cb3bc131970207246975ce.camel@kernel.org> (raw)
In-Reply-To: <62c5636814144fcdb61bb87f341232a0@intel.com>
On Wed, 2022-04-06 at 03:31 +0000, Zhang, Cathy wrote:
>
>
> > -----Original Message-----
> > From: Jarkko Sakkinen <jarkko@kernel.org>
> > Sent: Sunday, April 3, 2022 6:08 PM
> > To: Zhang, Cathy <cathy.zhang@intel.com>
> > Cc: linux-sgx@vger.kernel.org; x86@kernel.org; Chatre, Reinette
> > <reinette.chatre@intel.com>; Hansen, Dave <dave.hansen@intel.com>; Raj,
> > Ashok <ashok.raj@intel.com>
> > Subject: Re: [RFC PATCH v3 03/10] x86/sgx: Save enclave pointer for VA page
> >
> > On Fri, Apr 01, 2022 at 10:24:02PM +0800, Cathy Zhang wrote:
> > > Tearing down all enclaves is required by SGX SVN update, which
> > > involves running the ENCLS[EREMOVE] instruction on every EPC page.
> > > This (tearing down all enclaves) should be coordinated with any
> > > enclaves that may be in the process of existing and thus already be
> > > running ENCLS[EREMOVE] as part of enclave release.
> > >
> > > In support of this coordination, it is required to know which enclave
> > > owns each in-use EPC page. It is already possible to locate the owning
> > > enclave of SECS and regular pages but not for VA pages.
> > >
> > > Save the enclave pointer for each VA page to support locating its
> > > owning enclave.
> > >
> > > Note: to track 2T EPC memory, this scheme of tracking will use
> > > additional 8M memory.
> > >
> > > Signed-off-by: Cathy Zhang <cathy.zhang@intel.com>
> > > ---
> > > arch/x86/kernel/cpu/sgx/encl.h | 1 +
> > > arch/x86/kernel/cpu/sgx/ioctl.c | 1 +
> > > 2 files changed, 2 insertions(+)
> > >
> > > diff --git a/arch/x86/kernel/cpu/sgx/encl.h
> > > b/arch/x86/kernel/cpu/sgx/encl.h index 0c8571fc30cf..59fbd4ed5c64
> > > 100644
> > > --- a/arch/x86/kernel/cpu/sgx/encl.h
> > > +++ b/arch/x86/kernel/cpu/sgx/encl.h
> > > @@ -76,6 +76,7 @@ struct sgx_va_page {
> > > struct sgx_epc_page *epc_page;
> > > DECLARE_BITMAP(slots, SGX_VA_SLOT_COUNT);
> > > struct list_head list;
> > > + struct sgx_encl *encl;
> > > };
> > >
> > > struct sgx_backing {
> > > diff --git a/arch/x86/kernel/cpu/sgx/ioctl.c
> > > b/arch/x86/kernel/cpu/sgx/ioctl.c index f0ce96bd462a..da82abbb81b4
> > > 100644
> > > --- a/arch/x86/kernel/cpu/sgx/ioctl.c
> > > +++ b/arch/x86/kernel/cpu/sgx/ioctl.c
> > > @@ -30,6 +30,7 @@ static struct sgx_va_page *sgx_encl_grow(struct
> > sgx_encl *encl)
> > > if (!va_page)
> > > return ERR_PTR(-ENOMEM);
> > >
> > > + va_page->encl = encl;
> > > va_page->epc_page = sgx_alloc_va_page(va_page);
> > > if (IS_ERR(va_page->epc_page)) {
> > > err = ERR_CAST(va_page->epc_page);
> > > --
> > > 2.17.1
> > >
> >
> > Squash this with the previous patch. Then the code will provide
> > answer to one of the questions that I mentioned in 2/10 review.
> >
> > BR, Jarkko
>
> Squashed. How about re-write the commit log as follows:
>
> x86/sgx: Save enclave pointer for VA page
>
> Tearing down all enclaves is required by SGX SVN update, which
> involves running the ENCLS[EREMOVE] instruction on every EPC
> page. This (tearing down all enclaves) should be coordinated
> with any enclaves that may be in the process of existing and thus
> already be running ENCLS[EREMOVE] as part of enclave release.
>
> In support of this coordination, it is required to know which enclave
> owns each in-use EPC page. It is already possible to locate the
> owning enclave of SECS and regular pages but not for VA pages.
>
> Make the following changes for VA page's location:
> 1) Make epc->owner type-agnostic by change its type to 'void *'. So,
> besides "struct sgx_encl_page", it can have other types, like
> "struct sgx_va_page".
> 2) Save the enclave pointer for each VA page to support locating its
> owning enclave.
>
> Note: to track 2T EPC memory, this scheme of tracking will use
> additional 8M memory.
Sounds good to me.
BR, Jarkko
next prev parent reply other threads:[~2022-04-06 10:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 14:23 [RFC PATCH v3 00/10] Support microcode updates affecting SGX Cathy Zhang
2022-04-01 14:24 ` [RFC PATCH v3 01/10] x86/sgx: Introduce mechanism to prevent new initializations of EPC pages Cathy Zhang
2022-04-03 8:13 ` Jarkko Sakkinen
2022-04-06 3:31 ` Zhang, Cathy
2022-04-01 14:24 ` [RFC PATCH v3 02/10] x86/sgx: Provide VA page non-NULL owner Cathy Zhang
2022-04-03 8:29 ` Jarkko Sakkinen
2022-04-01 14:24 ` [RFC PATCH v3 03/10] x86/sgx: Save enclave pointer for VA page Cathy Zhang
2022-04-03 10:08 ` Jarkko Sakkinen
2022-04-06 3:31 ` Zhang, Cathy
2022-04-06 6:33 ` Jarkko Sakkinen [this message]
2022-04-01 14:24 ` [RFC PATCH v3 04/10] x86/sgx: Keep record for SGX VA and Guest page type Cathy Zhang
2022-04-03 10:11 ` Jarkko Sakkinen
2022-04-06 3:38 ` Zhang, Cathy
2022-04-01 14:24 ` [RFC PATCH v3 05/10] x86/sgx: Save the size of each EPC section Cathy Zhang
2022-04-03 10:14 ` Jarkko Sakkinen
2022-04-06 4:00 ` Zhang, Cathy
2022-04-06 6:34 ` Jarkko Sakkinen
2022-04-01 14:24 ` [RFC PATCH v3 06/10] x86/sgx: Forced EPC page zapping for EUPDATESVN Cathy Zhang
2022-04-03 10:20 ` Jarkko Sakkinen
2022-04-06 4:21 ` Zhang, Cathy
2022-04-01 14:24 ` [RFC PATCH v3 07/10] x86/sgx: Define error codes for ENCLS[EUPDATESVN] Cathy Zhang
2022-04-01 14:24 ` [RFC PATCH v3 08/10] x86/sgx: Implement ENCLS[EUPDATESVN] Cathy Zhang
2022-04-01 14:24 ` [RFC PATCH v3 09/10] x86/cpu: Call ENCLS[EUPDATESVN] procedure in microcode update Cathy Zhang
2022-04-01 14:29 ` Borislav Petkov
2022-04-02 2:54 ` Zhang, Cathy
2022-04-01 15:42 ` Dave Hansen
2022-04-02 3:02 ` Zhang, Cathy
2022-04-01 14:24 ` [RFC PATCH v3 10/10] x86/sgx: Call ENCLS[EUPDATESVN] during SGX initialization Cathy Zhang
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=e16bfc917ac85da8e2cb3bc131970207246975ce.camel@kernel.org \
--to=jarkko@kernel.org \
--cc=ashok.raj@intel.com \
--cc=cathy.zhang@intel.com \
--cc=dave.hansen@intel.com \
--cc=linux-sgx@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--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