From: Kai Huang <kai.huang@intel.com>
To: Dave Hansen <dave.hansen@intel.com>,
Zhiquan Li <zhiquan1.li@intel.com>,
linux-sgx@vger.kernel.org, tony.luck@intel.com,
jarkko@kernel.org, dave.hansen@linux.intel.com
Cc: seanjc@google.com, fan.du@intel.com, cathy.zhang@intel.com
Subject: Re: [PATCH v5 1/3] x86/sgx: Repurpose the owner field as the virtual address of virtual EPC page
Date: Fri, 22 Jul 2022 11:27:02 +1200 [thread overview]
Message-ID: <fa93057f417b1f630d8199381589c415a0ec710b.camel@intel.com> (raw)
In-Reply-To: <111cc85d-0e49-ad45-84e9-1a71ce58a2ca@intel.com>
On Thu, 2022-07-21 at 09:42 -0700, Dave Hansen wrote:
> On 6/22/22 02:37, Zhiquan Li wrote:
> > diff --git a/arch/x86/kernel/cpu/sgx/virt.c b/arch/x86/kernel/cpu/sgx/virt.c
> > index 6a77a14eee38..776ae5c1c032 100644
> > --- a/arch/x86/kernel/cpu/sgx/virt.c
> > +++ b/arch/x86/kernel/cpu/sgx/virt.c
> > @@ -46,10 +46,12 @@ static int __sgx_vepc_fault(struct sgx_vepc *vepc,
> > if (epc_page)
> > return 0;
> >
> > - epc_page = sgx_alloc_epc_page(vepc, false);
> > + epc_page = sgx_alloc_epc_page((void *)addr, false);
> > if (IS_ERR(epc_page))
> > return PTR_ERR(epc_page);
>
> Was the 'vepc' value simply unused before?
Yes for EPC page assigned to KVM guest it was unused before this series.
--
Thanks,
-Kai
next prev parent reply other threads:[~2022-07-21 23:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 9:37 [PATCH v5 0/3] x86/sgx: fine grained SGX MCA behavior Zhiquan Li
2022-06-22 9:37 ` [PATCH v5 1/3] x86/sgx: Repurpose the owner field as the virtual address of virtual EPC page Zhiquan Li
2022-07-21 16:42 ` Dave Hansen
2022-07-21 23:27 ` Kai Huang [this message]
2022-06-22 9:37 ` [PATCH v5 2/3] x86/sgx: Fine grained SGX MCA behavior for virtualization Zhiquan Li
2022-07-21 16:54 ` Dave Hansen
2022-07-22 16:21 ` Zhiquan Li
2022-06-22 9:37 ` [PATCH v5 3/3] x86/sgx: Fine grained SGX MCA behavior for normal case Zhiquan Li
2022-07-21 16:57 ` Dave Hansen
2022-07-22 17:28 ` Zhiquan Li
2022-06-26 6:04 ` [PATCH v5 0/3] x86/sgx: fine grained SGX MCA behavior 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=fa93057f417b1f630d8199381589c415a0ec710b.camel@intel.com \
--to=kai.huang@intel.com \
--cc=cathy.zhang@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=fan.du@intel.com \
--cc=jarkko@kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=seanjc@google.com \
--cc=tony.luck@intel.com \
--cc=zhiquan1.li@intel.com \
/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