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]

Message-ID: <20090106144843.GH16738@wotan.suse.de>
Date:	Tue, 6 Jan 2009 15:48:43 +0100
From:	Nick Piggin <npiggin@...e.de>
To:	Jack Steiner <steiner@....com>
Cc:	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 08:33:30AM -0600, 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.

Yeah.... I don't know. OTOH it would be more logical to enable
MAXSMP iff UV is enabled (or change the MAXSMP limits for when
UV is enabled). Or you could select Intel CPUs if UV is enabled,
or disable GRU if UV is not set etc etc.

I didn't want to get too fancy with config options because arbitrary
linkages seem to just cause headaches. I figure if someone wants
to enable it, they can do so.

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