From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Tony W Wang-oc <TonyWWang-oc@zhaoxin.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org,
DavidWang@zhaoxin.com, CooperYan@zhaoxin.com,
QiyuanWang@zhaoxin.com, HerryYang@zhaoxin.com
Subject: Re: [PATCH] x86/Kconfig: Make X86_UMIP to cover Zhaoxin CPUs too
Date: Wed, 4 Mar 2020 09:13:36 -0800 [thread overview]
Message-ID: <20200304171336.GD21662@linux.intel.com> (raw)
In-Reply-To: <1583288285-2804-1-git-send-email-TonyWWang-oc@zhaoxin.com>
On Wed, Mar 04, 2020 at 10:18:05AM +0800, Tony W Wang-oc wrote:
> New Zhaoxin family 7 CPUs support the UMIP (User-Mode Instruction
> Prevention) feature. So, modify X86_UMIP depends on Zhaoxin CPUs too.
>
> Signed-off-by: Tony W Wang-oc <TonyWWang-oc@zhaoxin.com>
> ---
> arch/x86/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 16a4b39..ca4beb8 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -1877,7 +1877,7 @@ config X86_SMAP
>
> config X86_UMIP
> def_bool y
> - depends on CPU_SUP_INTEL || CPU_SUP_AMD
> + depends on CPU_SUP_INTEL || CPU_SUP_AMD || CPU_SUP_CENTAUR || CPU_SUP_ZHAOXIN
The changelog only mentions Zhaoxin, but this also adds Centaur...
> prompt "User Mode Instruction Prevention" if EXPERT
> ---help---
> User Mode Instruction Prevention (UMIP) is a security feature in
> --
> 2.7.4
>
next prev parent reply other threads:[~2020-03-04 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 2:18 [PATCH] x86/Kconfig: Make X86_UMIP to cover Zhaoxin CPUs too Tony W Wang-oc
2020-03-04 17:13 ` Sean Christopherson [this message]
2020-03-05 3:40 ` Tony W Wang-oc
2020-03-05 15:59 ` Sean Christopherson
2020-03-06 9:14 ` Tony W Wang-oc
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=20200304171336.GD21662@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=CooperYan@zhaoxin.com \
--cc=DavidWang@zhaoxin.com \
--cc=HerryYang@zhaoxin.com \
--cc=QiyuanWang@zhaoxin.com \
--cc=TonyWWang-oc@zhaoxin.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.