linux-kernel - Re: [PATCH v1 0/2] x86/Kconfig: modify X86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 6 Mar 2020 17:12:50 +0800
From:   Tony W Wang-oc <TonyWWang-oc@...oxin.com>
To:     Sean Christopherson <sean.j.christopherson@...el.com>
CC:     <tglx@...utronix.de>, <mingo@...hat.com>, <bp@...en8.de>,
        <hpa@...or.com>, <x86@...nel.org>, <linux-kernel@...r.kernel.org>,
        <DavidWang@...oxin.com>, <CooperYan@...oxin.com>,
        <QiyuanWang@...oxin.com>, <HerryYang@...oxin.com>
Subject: Re: [PATCH v1 0/2] x86/Kconfig: modify X86_UMIP depends on CPUs


On 05/03/2020 23:51, Sean Christopherson wrote:
> 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?

While the UMIP is a generic X86 CPU feature, I think this way is better.

Sincerely
TonyWWang-oc
> 
>> 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
>>
> .
>