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 v1 0/2] x86/Kconfig: modify X86_UMIP depends on CPUs
Date: Thu, 5 Mar 2020 07:51:15 -0800 [thread overview]
Message-ID: <20200305155115.GC11500@linux.intel.com> (raw)
In-Reply-To: <1583390951-4103-1-git-send-email-TonyWWang-oc@zhaoxin.com>
On Thu, Mar 05, 2020 at 02:49:09PM +0800, Tony W Wang-oc wrote:
> CONFIG_X86_UMIP is generic since commit b971880fe79f (x86/Kconfig:
> Rename UMIP config parameter).
>
> Some Centaur family 7 CPUs and Zhaoxin family 7 CPUs support the UMIP
> feature. So, modify X86_UMIP to cover these CPUs too.
That leaves UMC_32, TRANSMETA_32 and CYRIX_32 as the last CPU_SUP types
that don't support UMIP. Maybe it's time to remove the CPU_SUP checks
altogether, same as X86_SMAP?
> Tony W Wang-oc (2):
> x86/Kconfig: Make X86_UMIP to cover Centaur CPUs
> x86/Kconfig: Make X86_UMIP to cover Zhaoxin CPUs
>
> arch/x86/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --
> 2.7.4
>
next prev parent reply other threads:[~2020-03-05 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 6:49 [PATCH v1 0/2] x86/Kconfig: modify X86_UMIP depends on CPUs Tony W Wang-oc
2020-03-05 6:49 ` [PATCH v1 1/2] x86/Kconfig: Make X86_UMIP to cover Centaur CPUs Tony W Wang-oc
2020-03-05 6:49 ` [PATCH v1 2/2] x86/Kconfig: Make X86_UMIP to cover Zhaoxin CPUs Tony W Wang-oc
2020-03-05 15:51 ` Sean Christopherson [this message]
2020-03-06 9:12 ` [PATCH v1 0/2] x86/Kconfig: modify X86_UMIP depends on CPUs 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=20200305155115.GC11500@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.