[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM5PR12MB2471E24B40B96E3863B69955957E0@DM5PR12MB2471.namprd12.prod.outlook.com>
Date: Tue, 5 Nov 2019 01:43:09 +0000
From: "Moger, Babu" <Babu.Moger@....com>
To: Borislav Petkov <bp@...en8.de>
CC: "tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"hpa@...or.com" <hpa@...or.com>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
"rkrcmar@...hat.com" <rkrcmar@...hat.com>,
"sean.j.christopherson@...el.com" <sean.j.christopherson@...el.com>,
"vkuznets@...hat.com" <vkuznets@...hat.com>,
"wanpengli@...cent.com" <wanpengli@...cent.com>,
"jmattson@...gle.com" <jmattson@...gle.com>,
"x86@...nel.org" <x86@...nel.org>,
"joro@...tes.org" <joro@...tes.org>,
"luto@...nel.org" <luto@...nel.org>,
"zohar@...ux.ibm.com" <zohar@...ux.ibm.com>,
"yamada.masahiro@...ionext.com" <yamada.masahiro@...ionext.com>,
"nayna@...ux.ibm.com" <nayna@...ux.ibm.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>
Subject: RE: [PATCH v2] x86/Kconfig: Rename UMIP config parameter
> -----Original Message-----
> From: Borislav Petkov <bp@...en8.de>
> Sent: Monday, November 4, 2019 3:48 PM
> To: Moger, Babu <Babu.Moger@....com>
> Cc: tglx@...utronix.de; mingo@...hat.com; hpa@...or.com;
> pbonzini@...hat.com; rkrcmar@...hat.com; sean.j.christopherson@...el.com;
> vkuznets@...hat.com; wanpengli@...cent.com; jmattson@...gle.com;
> x86@...nel.org; joro@...tes.org; luto@...nel.org; zohar@...ux.ibm.com;
> yamada.masahiro@...ionext.com; nayna@...ux.ibm.com; linux-
> kernel@...r.kernel.org; kvm@...r.kernel.org
> Subject: Re: [PATCH v2] x86/Kconfig: Rename UMIP config parameter
>
> On Mon, Nov 04, 2019 at 08:50:51PM +0000, Moger, Babu wrote:
> > AMD 2nd generation EPYC processors support the UMIP (User-Mode
> > Instruction Prevention) feature. So, rename X86_INTEL_UMIP to
> > generic X86_UMIP and modify the text to cover both Intel and AMD.
> >
> > Signed-off-by: Babu Moger <babu.moger@....com>
> > ---
> > v2:
> > Learned that for the hardware that support UMIP, we dont need to
> > emulate. Removed the emulation related code and just submitting
> > the config changes.
> >
> > arch/x86/Kconfig | 8 ++++----
> > arch/x86/include/asm/disabled-features.h | 2 +-
> > arch/x86/include/asm/umip.h | 4 ++--
> > arch/x86/kernel/Makefile | 2 +-
> > 4 files changed, 8 insertions(+), 8 deletions(-)
> >
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index d6e1faa28c58..821b7cebff31 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -1880,13 +1880,13 @@ config X86_SMAP
> >
> > If unsure, say Y.
> >
> > -config X86_INTEL_UMIP
> > +config X86_UMIP
> > def_bool y
> > - depends on CPU_SUP_INTEL
> > - prompt "Intel User Mode Instruction Prevention" if EXPERT
> > + depends on X86 && (CPU_SUP_INTEL || CPU_SUP_AMD)
> ^^^
>
> What's the dependency on X86 for?
>
> Aren't the CPU_SUP_* things enough?
Yes. It should be good enough. Will update.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists