From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: make generic arch support NUMAQ v2
Date: Fri, 6 Jun 2008 16:09:47 +0200 [thread overview]
Message-ID: <20080606140947.GA29104@elte.hu> (raw)
In-Reply-To: <86802c440806052327v14428d4dhf54e13874c1f0a5a@mail.gmail.com>
* Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> > It is my understanding that special support for NUMAQ should die, so
> > the only remaning usage of CONFIG_NUMAQ is if set to select
> > GENERICARCH. In other words that you should not use CONFIG_NUMAQ
> > anywhere in the code but solely rely on GENERICARCH and then do
> > runtime detection of the other things.
>
> in case someone don't want to build that special numaq code in.
>
> I think we should make ES7000, Summit depend to GENERICARCH too.
correct. If someone wants more restricted support, pure CONFIG_X86_PC
should do that fine.
also, even GENERICARCH should have as little Kconfig implications as
possible. I.e. before your cleanups the subarch code was used to
implement something very non-PC, and it was done build-time - which is a
PITA in terms of testing and in terms of general complexity. We want to
remove those complications and eventually we want to remove the subarch
code altogether. (without narrowing hw support of course)
Ingo
next prev parent reply other threads:[~2008-06-06 14:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 10:09 RFC [PATCH] x86: make generic arch support NUMAQ Yinghai Lu
2008-06-05 11:00 ` Sam Ravnborg
2008-06-05 12:39 ` Ingo Molnar
2008-06-05 17:33 ` Yinghai Lu
2008-06-05 17:26 ` Yinghai Lu
2008-06-06 0:14 ` [PATCH] x86: make generic arch support NUMAQ v2 Yinghai Lu
2008-06-06 0:54 ` Yinghai Lu
2008-06-06 6:17 ` Sam Ravnborg
2008-06-06 6:27 ` Yinghai Lu
2008-06-06 14:09 ` Ingo Molnar [this message]
2008-06-06 18:05 ` Yinghai Lu
2008-06-06 21:41 ` [PATCH] x86: make generic arch support NUMAQ v3 Yinghai Lu
2008-06-07 7:31 ` [PATCH] x86: make generic arch support NUMAQ v4 Yinghai Lu
2008-06-09 1:29 ` [PATCH] x86: introduce max_physical_apicid for bigsmp switching Yinghai Lu
2008-06-10 9:53 ` Ingo Molnar
2008-06-09 1:31 ` [PATCH] x86: make generic arch support NUMAQ v5 Yinghai Lu
2008-06-09 14:41 ` Andy Whitcroft
2008-06-09 18:00 ` Yinghai Lu
2008-06-10 0:00 ` [PATCH] x86: make generic arch support NUMAQ - fix Yinghai Lu
2008-06-10 1:11 ` [PATCH] x86: make generic arch support NUMAQ - fix #2 Yinghai Lu
2008-06-10 9:55 ` [PATCH] x86: make generic arch support NUMAQ v5 Ingo Molnar
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=20080606140947.GA29104@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--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
Powered by JetHome