From: "Zhang, Cathy" <cathy.zhang@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"jarkko@kernel.org" <jarkko@kernel.org>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"Raj, Ashok" <ashok.raj@intel.com>,
"Peng, Chao P" <chao.p.peng@intel.com>,
"Zhong, Yang" <yang.zhong@intel.com>
Subject: RE: [PATCH v4 8/9] x86/cpu: Call ENCLS[EUPDATESVN] procedure in microcode update
Date: Sun, 24 Apr 2022 02:18:13 +0000 [thread overview]
Message-ID: <8004820093324bb8974d95b864bb7633@intel.com> (raw)
In-Reply-To: <YmFI7OiWRaWNNsGM@zn.tnic>
Hi Boris,
> -----Original Message-----
> From: Borislav Petkov <bp@alien8.de>
> Sent: Thursday, April 21, 2022 8:07 PM
> To: Zhang, Cathy <cathy.zhang@intel.com>
> Cc: linux-sgx@vger.kernel.org; x86@kernel.org; jarkko@kernel.org; Chatre,
> Reinette <reinette.chatre@intel.com>; Hansen, Dave
> <dave.hansen@intel.com>; Raj, Ashok <ashok.raj@intel.com>; Peng, Chao P
> <chao.p.peng@intel.com>; Zhong, Yang <yang.zhong@intel.com>
> Subject: Re: [PATCH v4 8/9] x86/cpu: Call ENCLS[EUPDATESVN] procedure in
> microcode update
>
> On Thu, Apr 21, 2022 at 07:03:25PM +0800, Cathy Zhang wrote:
> > diff --git a/arch/x86/include/asm/microcode.h
> b/arch/x86/include/asm/microcode.h
> > index d6bfdfb0f0af..ec12392af371 100644
> > --- a/arch/x86/include/asm/microcode.h
> > +++ b/arch/x86/include/asm/microcode.h
> > @@ -3,6 +3,7 @@
> > #define _ASM_X86_MICROCODE_H
> >
> > #include <asm/cpu.h>
> > +#include <asm/sgx.h>
>
> That include looks like a leftover.
Yep, it is. I've removed. Thanks for pointing out! I will pay more attention in future.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-04-24 2:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 11:03 [PATCH v4 0/9] Support microcode updates affecting SGX Cathy Zhang
2022-04-21 11:03 ` [PATCH v4 1/9] x86/sgx: Introduce mechanism to prevent new initializations of EPC pages Cathy Zhang
2022-04-21 16:02 ` Jarkko Sakkinen
2022-04-24 2:27 ` Zhang, Cathy
2022-04-25 14:00 ` Jarkko Sakkinen
2022-04-21 11:03 ` [PATCH v4 2/9] x86/sgx: Save enclave pointer for VA page Cathy Zhang
2022-04-21 16:04 ` Jarkko Sakkinen
2022-04-24 2:31 ` Zhang, Cathy
2022-04-21 11:03 ` [PATCH v4 3/9] x86/sgx: Keep record for SGX VA and Guest page type Cathy Zhang
2022-04-21 11:03 ` [PATCH v4 4/9] x86/sgx: Save the size of each EPC section Cathy Zhang
2022-04-21 11:03 ` [PATCH v4 5/9] x86/sgx: Forced EPC page zapping for EUPDATESVN Cathy Zhang
2022-04-21 16:07 ` Jarkko Sakkinen
2022-04-24 2:32 ` Zhang, Cathy
2022-04-21 11:03 ` [PATCH v4 6/9] x86/sgx: Define error codes for ENCLS[EUPDATESVN] Cathy Zhang
2022-04-21 11:03 ` [PATCH v4 7/9] x86/sgx: Implement ENCLS[EUPDATESVN] Cathy Zhang
2022-04-21 11:03 ` [PATCH v4 8/9] x86/cpu: Call ENCLS[EUPDATESVN] procedure in microcode update Cathy Zhang
2022-04-21 12:07 ` Borislav Petkov
2022-04-24 2:18 ` Zhang, Cathy [this message]
2022-04-21 11:03 ` [PATCH v4 9/9] 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=8004820093324bb8974d95b864bb7633@intel.com \
--to=cathy.zhang@intel.com \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=chao.p.peng@intel.com \
--cc=dave.hansen@intel.com \
--cc=jarkko@kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=x86@kernel.org \
--cc=yang.zhong@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