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: <eada2a070901291324t1a2dbb08hbff7b026c77d69cd@mail.gmail.com>
Date:	Thu, 29 Jan 2009 13:24:34 -0800
From:	Tim Pepper <lnxninja@...ux.vnet.ibm.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: x86: unify genapic code, unify subarchitectures, remove old 
	subarchitecture code

On Thu, Jan 29, 2009 at 6:02 AM, Andi Kleen <andi@...stfloor.org> wrote:
> My suggestion would be to deprecate and then remove es7000 and
> numaq too. The es7000 subarch is only for very old es7000 systems (the
> newer ones all work with bigsmp) and I expect the user base is very
> likely zero or very near it. For NUMAQ it's similar -- there's
> apparently one system left at IBM, and I'm sure IBM can find some
> replacement. Especially NUMAQ has some ugly ifdefery outside the
> subarch code too that would be good to remove. Overall that would
> be a good cleanup without impacting the user base really.

The machines (yes plural!) on which we had regular testing happening
have been offline for a few months due to some broader dependencies
(eg: console server in the old product used an old version of windows
that doesn't meet the corporate security standards) and we've just not
managed to get past that.  That in turn is in the way of debugging
boot issues with newer kernels.  At this point the most passionate
Sequent/IBMers caring about the NUMAQ support are resigned to it being
a lost cause.

The main benefit to carrying NUMAQ support along this long was these
machines had a knack for triggering real bugs.  But since there's no
active bug testing happening on them now and it doesn't look like
there will be...

RIP NUMAQ!   (sorry dhansen and apw :)

I believe in the past there've been some let's kill off NUMAQ patches
floated...if anybody has something that applies, go for it.  Else
we'll post something shortly.




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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ