linux-kernel - Re: Genapic cleanup & NUMAQ/es7000 removal

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

Date:	Thu, 5 Feb 2009 22:25:25 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Andi Kleen <andi@...stfloor.org>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Cc:	Tim Pepper <tpepper@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: Genapic cleanup & NUMAQ/es7000 removal

* Andi Kleen <andi@...stfloor.org> wrote:

> > I'm not going to apply that series for the reasons i outlined in the NUMAQ 
> > discussion already. The runtime callbacks arent really a maintenance 
> > problem: most of them are in boot code so it's not a runtime overhead issue.
> 
> Ok.  It's basically dead code now, dropping it would just make
> the kernels a little smaller and also the code somewhat easier
> to read.
> 
> If you keep them I would be interested in hearing about your testing plan 
> for es7000 and NUMAQ AFAIK there is noone currently running them which
> makes that likely challenging.

For example we havent had reports about boot hangs with certain rare types 
of Cyrix CPU based boards (obsolete, desupported, manufacturer gone) for 
multiple stable kernel releases - still eventually someone came across the 
problem and a fix was done. The testing exposure of the upstream kernel is 
still very narrow in practice.

Anyway, i stated our maintenance position about x86 compatibility clearly 
and unless there's some good technical reason for the removal the code stays 
in the kernel.

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