linux-kernel - Re: [patch] x86: make UV support optional

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]

Date:	Tue, 6 Jan 2009 16:04:44 +0100
From:	Nick Piggin <npiggin@...e.de>
To:	Mike Travis <travis@....com>
Cc:	Jack Steiner <steiner@....com>, tglx@...utronix.de,
	mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org,
	Cliff Wickman <cpw@....com>, Russ Anderson <rja@....com>
Subject: Re: [patch] x86: make UV support optional

On Tue, Jan 06, 2009 at 06:54:08AM -0800, Mike Travis wrote:
> Jack Steiner wrote:
> > On Tue, Jan 06, 2009 at 07:03:48AM +0100, Nick Piggin wrote:
> >> UV is fairly rare.... and much of the support is already there to cope with
> >> 32-bit builds. So this makes sense I think.
> >>
> > 
> > 
> > Looks ok to me. One suggestion though. There is a MAXSMP config
> > option. I would suggest enabling UV if MAXSMP is enabled. This
> > will help ensure that UV is tested more frequently & may minimize
> > regressions.
> > 
> > 
> > --- jack
> 
> Nick - would you add something like this to your patch?  Thanks! Mike
> ---
> Subject: x86: enable UV when MAXSMP is configured.
> 
> We want UV code to be tested even for non-UV architectures.  Enabling
> MAXSMP specifies "maximizing the system capabitlity" and UV is one of
> these methods.  Also helps distros select the correct config options
> for their default configurations.

I don't really follow. The config option I added is very visible and
clear, isn't it? I don't think MAXSMP means that, otherwise it would
basically be allyesconfig.

I wouldn't object to have a platform types menu like the processor
types one. Or a generic architecture checkbox to select some of
these things together.

--
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/