linux-kernel - Re: x86: unify genapic code, unify subarchitectures, remove old subarchitecture code

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:	Thu, 29 Jan 2009 14:58:28 -0800
From:	Tim Pepper <lnxninja@...ux.vnet.ibm.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Andi Kleen <andi@...stfloor.org>, 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 2:14 PM, Ingo Molnar <mingo@...e.hu> wrote:
> At this point there's no technical need to kill it - it's a zero-overhead
> thing tucked away into a single .c module in arch/x86/kernel/numaq_32.c. I
> even consolidated most of its headers in that file, to reduce its cross
> section.

Wish we'd have piped up earlier to save you a bit of work.

> So two days ago it might have made some sense to rip out this code - now
> there's no pressing need really. We can remove it in a few years once the
> last beep has been received from those platforms. The numaq code is now
> quite similar to an old driver in drivers/* - there's no real downside
> from having it around.

We can make the NUMAQ's beep still, if not boot.  :)

Reality is they're just not worth the effort any more and there's no
sign of anybody else having them.  Assuming your code goes in for
2.6.30 it'll be easy to drop NUMAQ support.  Even if there's not much
downside there's also not much reason to leave it in but marked
deprecated/broken.



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/