From: Magnus Damm <magnus.damm@gmail.com>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, Ravikiran G Thirumalai <kiran@scalex86.org>,
linux-kernel@vger.kernel.org,
"Shai Fultheim (Shai@scalex86.org)" <shai@scalex86.org>
Subject: Re: [discuss] [rfc] x86_64: Kconfig changes for NUMA
Date: Thu, 27 Oct 2005 17:25:12 +0900 [thread overview]
Message-ID: <aec7e5c30510270125q1e175daeoeaea99584f305261@mail.gmail.com> (raw)
In-Reply-To: <200510270950.13268.ak@suse.de>
On 10/27/05, Andi Kleen <ak@suse.de> wrote:
> On Thursday 27 October 2005 08:25, Magnus Damm wrote:
>
> > > While at it, could you please consider to remove the SMP dependency
> > > from NUMA_EMU? 2.6.14-rc5-git5 builds and works with !SMP and
>
> No.
That was quick.
> > > NUMA_EMU.
> > >
> > > Why?
> > > 1. No need to force SMP when not needed.
> > > 2. qemu-system-x86_64 does not currently work with SMP kernels.
>
> qemu needs to be fixed then.
Yep. Any day soon now (tm).
> > Update:
> >
> > Both CONFIG_NUMA_EMU and CONFIG_K8_NUMA build and run just fine
> > without CONFIG_SMP. Not sure about CONFIG_ACPI_NUMA though.
>
> I don't want too many weird combinations which no normal person uses like
> this. Undoubtedly there will be compile breakage for such stuff in the future
> (even if it happens to work by chance now) and best is to not open this can
> of worms in the first place. The number of variants has to be kept under
> control.
Yes, I understand that keeping the combinations low is a good thing.
But if the same logic is applied to the NUMA code, why then is there
both k8topology.c and srat.c? Does non-ACPI systems exist in x86_64
land?
Thanks,
/ magnus
next prev parent reply other threads:[~2005-10-27 8:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 7:09 Ravikiran G Thirumalai
2005-10-26 14:46 ` [discuss] " Andi Kleen
2005-10-26 20:20 ` Ravikiran G Thirumalai
2005-10-26 21:39 ` Andi Kleen
2005-10-27 1:40 ` Magnus Damm
2005-10-27 6:25 ` Magnus Damm
2005-10-27 7:50 ` Andi Kleen
2005-10-27 8:25 ` Magnus Damm [this message]
2005-10-27 8:31 ` Andi Kleen
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=aec7e5c30510270125q1e175daeoeaea99584f305261@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shai@scalex86.org \
/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
all inboxes | Powered by JetHome®