linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
	Jack Steiner <steiner@sgi.com>, Andi Kleen <andi@firstfloor.org>,
	tglx@linutronix.de, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC 8/8] x86_64: Support for new UV apic
Date: Mon, 31 Mar 2008 14:52:13 +0200	[thread overview]
Message-ID: <20080331125213.GF29105@one.firstfloor.org> (raw)
In-Reply-To: <20080331123338.GA14636@elte.hu>

>  - 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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-03-31 12:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 18:21 Jack Steiner
2008-03-25 10:25 ` Andi Kleen
2008-03-25 17:56   ` Jack Steiner
2008-03-25 18:06     ` Andi Kleen
2008-03-26  2:23       ` Jeremy Fitzhardinge
2008-03-26  3:22         ` Glauber Costa
2008-03-26  7:29         ` Ingo Molnar
2008-03-26  7:38     ` Ingo Molnar
2008-03-30 20:23       ` Yinghai Lu
2008-03-30 21:03         ` Jack Steiner
2008-03-30 21:18           ` Andi Kleen
2008-03-30 23:29             ` Yinghai Lu
2008-03-31  2:18               ` Jack Steiner
2008-03-31  2:20                 ` Yinghai Lu
2008-03-31 12:33                   ` Ingo Molnar
2008-03-31 12:52                     ` Andi Kleen [this message]
2008-03-31 18:42                     ` Yinghai Lu
2008-03-31  6:48               ` Andi Kleen
2008-03-25 14:30 ` Ingo Molnar
2008-03-25 16:31   ` Jack Steiner
2008-03-26  3:24     ` Glauber Costa
2008-03-30 20:41 ` Yinghai Lu
2008-03-30 21:08   ` Jack Steiner
2008-03-30 23:24     ` Yinghai Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080331125213.GF29105@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=steiner@sgi.com \
    --cc=tglx@linutronix.de \
    --cc=yhlu.kernel@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox