linux-kernel - Re: Voyager phys_cpu_present

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: <20080422152509.GE26446@shadowen.org>
Date:	Tue, 22 Apr 2008 16:25:09 +0100
From:	Andy Whitcroft <apw@...dowen.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>, mingo@...e.hu, bunk@...nel.org,
	astarikovskiy@...e.de, tglx@...utronix.de,
	James.Bottomley@...senPartnership.com, linux-kernel@...r.kernel.org
Subject: Re: Voyager phys_cpu_present_map compile error

On Tue, Apr 22, 2008 at 06:29:27AM -0700, Andrew Morton wrote:
> > On Mon, 21 Apr 2008 08:55:36 -0400 "H. Peter Anvin" <hpa@...or.com> wrote:
> >
> > If there are no VISWS' left, we should just unload the code.
> 
> yup, it's a desirable objective.
> 
> I have a suspicion that there are no NUMAQs left either.  Andy, would it be
> missed?

Cirtainly these boxes are getting near end-of-life.  I am not sure how
many are out there beyond our the ones we have in the lab.  We do
maintain regular testing on them, even reporting them to TKO.

The main reason we bother keeping them working is that they have a large
numa ratio and tend to show up issues with other things, like the numa
scheduler issues when we got that latest re-write.

I has always been a shame that support wasn't included in generic, and
as a result we have ended up with this three way split "generic, voyager,
and numaq".  It made sense at the time for developers, but never did for
those down the food chain; particularly for distros.

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