public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Keith Mannthey <kmannth@us.ibm.com>,
	Andrew Morton <akpm@osdl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [Bugme-new] [Bug 2019] New: Bug from the mm subsystem	involving X  (fwd)
Date: 06 Feb 2004 09:22:49 -0800	[thread overview]
Message-ID: <1076088169.29478.2928.camel@nighthawk> (raw)
In-Reply-To: <5450000.1076082574@[10.10.2.4]>

On Fri, 2004-02-06 at 07:49, Martin J. Bligh wrote:
> >> +#ifdef CONFIG_NUMA
> >> +	#ifdef CONFIG_X86_NUMAQ
> >> +		#include <asm/numaq.h>
> >> +	#else	/* summit or generic arch */
> >> +		#include <asm/srat.h>
> >> +	#endif
> >> +#else /* !CONFIG_NUMA */
> >> +	#define get_memcfg_numa get_memcfg_numa_flat
> >> +	#define get_zholes_size(n) (0)
> >> +#endif /* CONFIG_NUMA */
> > 
> > We ran into a bug with #ifdefs like this before.  It was fixed in some
> > of the code that you're trying to remove.
> 
> What bug?

With a regular PC config, plus CONFIG_NUMA turned on:
  CC      arch/i386/kernel/process.o
In file included from include/asm/mmzone.h:17,
                 from include/linux/mmzone.h:318,
                 from include/linux/gfp.h:4,
                 from include/linux/slab.h:15,
                 from include/linux/percpu.h:4,
                 from include/linux/sched.h:31,
                 from include/linux/module.h:10,
                 from init/do_mounts.c:1:
include/asm/srat.h:31: #error CONFIG_ACPI_SRAT not defined, and srat.h
header has been included
In file included from include/asm/mmzone.h:17,
                 from include/linux/mmzone.h:318,
                 from include/linux/gfp.h:4,
                 from include/linux/slab.h:15,
                 from include/linux/percpu.h:4,
                 from include/linux/rcupdate.h:42,
                 from include/linux/dcache.h:10,
                 from include/linux/fs.h:17,
                 from init/do_mounts_initrd.c:3:

I can post the config if you like.  You were the one who made me go fix
it in the first place.  That's why I added that #error. :)

--dave


  reply	other threads:[~2004-02-06 17:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-04 23:17 [Bugme-new] [Bug 2019] New: Bug from the mm subsystem involving X (fwd) Martin J. Bligh
2004-02-04 23:58 ` Linus Torvalds
2004-02-05  0:12   ` Martin J. Bligh
2004-02-05  0:36     ` Martin J. Bligh
2004-02-05  0:43       ` Linus Torvalds
2004-02-05  0:56         ` Andrew Morton
2004-02-05  1:29           ` Linus Torvalds
2004-02-05  1:56             ` Keith Mannthey
2004-02-05  2:04               ` Linus Torvalds
2004-02-05  2:33                 ` Keith Mannthey
2004-02-05  2:47                   ` Linus Torvalds
2004-02-06  7:17                 ` Martin J. Bligh
2004-02-06  7:19                   ` Martin J. Bligh
2004-02-06  9:57                   ` Dave Hansen
2004-02-06 15:49                     ` Martin J. Bligh
2004-02-06 17:22                       ` Dave Hansen [this message]
2004-02-06 19:59                         ` Martin J. Bligh
2004-02-06 20:16                           ` Linus Torvalds
2004-02-06 21:18                             ` Martin J. Bligh
     [not found] <51080000.1075936626@flay.suse.lists.linux.kernel>
     [not found] ` <Pine.LNX.4.58.0402041539470.2086@home.osdl.org.suse.lists.linux.kernel>
     [not found]   ` <60330000.1075939958@flay.suse.lists.linux.kernel>
     [not found]     ` <64260000.1075941399@flay.suse.lists.linux.kernel>
     [not found]       ` <Pine.LNX.4.58.0402041639420.2086@home.osdl.org.suse.lists.linux.kernel>
     [not found]         ` <20040204165620.3d608798.akpm@osdl.org.suse.lists.linux.kernel>
     [not found]           ` <Pine.LNX.4.58.0402041719300.2086@home.osdl.org.suse.lists.linux.kernel>
     [not found]             ` <1075946211.13163.18962.camel@dyn318004bld.beaverton.ibm.com.suse.lists.linux.kernel>
     [not found]               ` <Pine.LNX.4.58.0402041800320.2086@home.osdl.org.suse.lists.linux.kernel>
     [not found]                 ` <98220000.1076051821@[10.10.2.4].suse.lists.linux.kernel>
     [not found]                   ` <1076061476.27855.1144.camel@nighthawk.suse.lists.linux.kernel>
     [not found]                     ` <5450000.1076082574@[10.10.2.4].suse.lists.linux.kernel>
     [not found]                       ` <1076088169.29478.2928.camel@nighthawk.suse.lists.linux.kernel>
     [not found]                         ` <218650000.1076097590@flay.suse.lists.linux.kernel>
     [not found]                           ` <Pine.LNX.4.58.0402061215030.30672@home.osdl.org.suse.lists.linux.kernel>
     [not found]                             ` <220850000.1076102320@flay.suse.lists.linux.kernel>
2004-02-07  3:54                               ` Andi Kleen
2004-02-07  4:49                                 ` Martin J. Bligh
2004-02-07  5:21                                   ` Andi Kleen
2004-02-07  6:37                                   ` Nick Piggin
2004-02-07  7:31                                     ` Martin J. Bligh

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=1076088169.29478.2928.camel@nighthawk \
    --to=haveblue@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=kmannth@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@aracnet.com \
    --cc=torvalds@osdl.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