Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Thu, 5 Mar 2020 07:51:15 -0800
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
Message-ID: <20200305155115.GC11500@linux.intel.com>
References: <1583390951-4103-1-git-send-email-TonyWWang-oc@zhaoxin.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1583390951-4103-1-git-send-email-TonyWWang-oc@zhaoxin.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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
>