[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20060825103507.4f2d193e.rdunlap@xenotime.net>
Date: Fri, 25 Aug 2006 10:35:07 -0700
From: "Randy.Dunlap" <rdunlap@...otime.net>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: another NUMA build error
On Fri, 25 Aug 2006 14:43:50 +0900 KAMEZAWA Hiroyuki wrote:
> On Thu, 24 Aug 2006 21:35:59 -0700
> "Randy.Dunlap" <rdunlap@...otime.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
-
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/
Powered by blists - more mailing lists