linux-kernel - Re: [RFC 8/8] x86_64: Support for new UV apic

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 31 Mar 2008 14:52:13 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>, Jack Steiner <steiner@....com>,
	Andi Kleen <andi@...stfloor.org>, tglx@...utronix.de,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC 8/8] x86_64: Support for new UV apic

>  - mach-voyager: obsolete.

You just have to convince James @)

> 
>  - mach-es7000: on the way out - latest ES7000's are generic.

That would mean dropping support for prev-gen es7000 which are not that
old actually (only a few years). But I think with a little effort the 
old es7000 code could be fit into the generic architecture. It is not
that far away from a normal PC.

> 
>  - mach-rdc321x: it's being de-sub-architectured. It's about one patch 
>                  away from becoming a non-subarch.

mach-numaq (not in arch, but spread out all over the port) 
	I hear there are only a one or two machines running left.
	Unfortunately they are in test.kernel.org, but hopefully
	they will die soon.
	NUMAQ has quite a lot of ugly ifdefs and special cases that would be 
	great to eliminate

mach-bigsmp/mach-summit (also in asm only)
	obsolete, should be deprecated for mach-generic
	(just generic currently pulls in code from them)
	A good first step would be to just disable the separate CONFIG
	options and only allow using them through generic.

-Andi

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