linux-kernel - Re: Comments on UV tlb flushing

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <488F6563.4000907@sgi.com>
Date:	Tue, 29 Jul 2008 11:45:55 -0700
From:	Mike Travis <travis@....com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	Yinghai Lu <yhlu.kernel@...il.com>, Cliff Wickman <cpw@....com>,
	Nick Piggin <nickpiggin@...oo.com.au>, steiner@....com,
	mingo@...e.hu, linux-kernel@...r.kernel.org
Subject: Re: Comments on UV tlb flushing

Jeremy Fitzhardinge wrote:
> Yinghai Lu wrote:
>> On Tue, Jul 29, 2008 at 7:43 AM, Jeremy Fitzhardinge <jeremy@...p.org>
>> wrote:
>>  
>>> Cliff Wickman wrote:
>>>    
>>>> I think that the Linux distributions are not going to build a special
>>>> UV kernel, are they?  So every distro would have to be prompted to
>>>> turn on
>>>> CONFIG_X86_UV, or else their kernel is not going to boot on UV.
>>>>
>>>>       
>>> Distros will generally turn on everything.  You could have it on by
>>> default
>>> if the kernel is built for CONFIG_X86_GENERICARCH which enables
>>> support for
>>> other big numa configurations.  I think distros generally build with
>>> that
>>> enabled anyway.
>>>     
>>
>> config X86_GENERICARCH
>>        bool "Generic architecture"
>>         depends on X86_32
>>   
> 
> Ah, overlooked that.
> 
> OK, well, either way it still needs to be a separate config option.
> 
>    J

Should there be a "generic" X86_ENTERPRISE_ARCH which turns on various
capabilities?  Our licenses and support agreements with SuSE and RH are
for their "Enterprise Editions" though the customer is free to run
whatever (unsupported from us).  Asking distros to enable that option
should be a no-brainer.  And it could be defaulted ON with the comment
to turn it off if you have a small desktop system.  This way they won't
forget... ;-)  [Actually, this could turn on MAXSMP as well.]

Thanks,
Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/