From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: another NUMA build error
Date: Fri, 25 Aug 2006 10:35:07 -0700 [thread overview]
Message-ID: <20060825103507.4f2d193e.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060825144350.27530dfb.kamezawa.hiroyu@jp.fujitsu.com>
On Fri, 25 Aug 2006 14:43:50 +0900 KAMEZAWA Hiroyuki wrote:
> On Thu, 24 Aug 2006 21:35:59 -0700
> "Randy.Dunlap" <rdunlap@xenotime.net> wrote:
>
> > Hi,
> > I was just trying to reproduce that 'register_one_node'
> > build error (and couldn't even with the supplied .config file;
> > weird). Anyway, after I enabled CONFIG_NUMA (but not CONFIG_ACPI),
> > I got the following error message. Seems that some config
> > options should prevent this config from even being possible
> > to create. Any ideas or suggestions?
> >
> Hi, there are 2 ways.
>
> 1. allow only 2 configs for i386/NUMA
> - CONFIG_NUMA + CONFIG_ACPI + CONFIG_ACPI_SRAT
> - CONFIG_NUMA + CONFIG_X86_NUMAQ
> 2. allow this and fix include/asm-i386/mmzone.h
> - CONFIG_NUMA + !CONFIG_ACP
>
> Which is sane ?
I really can't answer that one. The people who care about
NUMA would have to do that. It just shouldn't be possible
to make a config with a build error like this.
OK, I prefer option 2 because it is more generic (not hardware-
specific). Someone else can prefer option 1 because it is
hardware-specific. :)
---
~Randy
next prev parent reply other threads:[~2006-08-25 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 4:35 Randy.Dunlap
2006-08-25 5:43 ` KAMEZAWA Hiroyuki
2006-08-25 17:35 ` Randy.Dunlap [this message]
2006-08-25 18:28 ` KAMEZAWA Hiroyuki
2006-08-25 19:06 ` Randy.Dunlap
[not found] ` <a762e240608251544t2e15ec8dq5a8f95f02eecb0a4@mail.gmail.com>
2006-08-25 23:01 ` Randy.Dunlap
2006-08-26 1:56 ` KAMEZAWA Hiroyuki
2006-08-26 4:17 ` Randy.Dunlap
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=20060825103507.4f2d193e.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.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®