All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-next@vger.kernel.org
Subject: Re: linux-next: x86 tree build failure
Date: Tue, 17 Jun 2008 08:45:59 +0200	[thread overview]
Message-ID: <20080617064559.GA23580@elte.hu> (raw)
In-Reply-To: <20080617060835.GA16162@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> > | commit d94325315f241f86bd07a2ce113cbf28dc98de72
> > | Author: Ingo Molnar <mingo@elte.hu>
> > | Date:   Thu May 1 09:51:47 2008 +0000
> > |
> > |     acpi-acpi_numa_init-build-fix
> > |
> > |     x86.git testing found the following build error on latest -git:
> > |
> > |     drivers/acpi/numa.c: In function 'acpi_numa_init':
> > |     drivers/acpi/numa.c:226: error: 'NR_NODE_MEMBLKS' undeclared (first use in
> > |     drivers/acpi/numa.c:226: error: (Each undeclared identifier is reported onl
> > |     drivers/acpi/numa.c:226: error: for each function it appears in.)

btw., googling for "error: 'NR_NODE_MEMBLKS' undeclared" jumps straight 
to the patch i posted to lkml long ago.

> note, if you cherry-pick that, you'll also need:
> 
> | commit aca9de453911d095a9701ee6ebbae7fd3d6c7c1e
> | Author: Russ Anderson <rja@sgi.com>
> | Date:   Fri May 16 10:02:06 2008 -0500
> |
> |     acpi: fix boot breakage on Altix

i double-checked that cherry-picking these two out-of-x86-scope fixes 
from a month ago (which we found during -tip build testing) into 
auto-x86-next gets allmodconfig going.

I'm reluctant to permanently put them into the x86 branches though, as 
they are 'out of scope' of arch/x86 and would make the branch eligible 
to be 'pruned' out of linux-next.

the two fixes are attached below.

	Ingo

---------------------->
commit d94325315f241f86bd07a2ce113cbf28dc98de72
Author: Ingo Molnar <mingo@elte.hu>
Date:   Thu May 1 09:51:47 2008 +0000

    acpi-acpi_numa_init-build-fix
    
    x86.git testing found the following build error on latest -git:
    
     drivers/acpi/numa.c: In function 'acpi_numa_init':
     drivers/acpi/numa.c:226: error: 'NR_NODE_MEMBLKS' undeclared (first use in this function)
     drivers/acpi/numa.c:226: error: (Each undeclared identifier is reported only once
     drivers/acpi/numa.c:226: error: for each function it appears in.)
    
    with this config:
    
     http://redhat.com/~mingo/misc/config-Wed_Apr_30_22_42_42_CEST_2008.bad
    
    i suspect we dont want SRAT parsing when CONFIG_HAVE_ARCH_PARSE_SRAT
    is unset - but the fix looks a bit ugly. Perhaps we should define
    NR_NODE_MEMBLKS even in this case and just let the code fall back
    to some sane behavior?
    
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

diff --git a/drivers/acpi/numa.c b/drivers/acpi/numa.c
index 5d59cb3..8cab8c5 100644
--- a/drivers/acpi/numa.c
+++ b/drivers/acpi/numa.c
@@ -176,6 +176,7 @@ acpi_parse_processor_affinity(struct acpi_subtable_header * header,
 	return 0;
 }
 
+#ifdef CONFIG_HAVE_ARCH_PARSE_SRAT
 static int __init
 acpi_parse_memory_affinity(struct acpi_subtable_header * header,
 			   const unsigned long end)
@@ -193,6 +194,7 @@ acpi_parse_memory_affinity(struct acpi_subtable_header * header,
 
 	return 0;
 }
+#endif
 
 static int __init acpi_parse_srat(struct acpi_table_header *table)
 {
@@ -221,9 +223,11 @@ int __init acpi_numa_init(void)
 	if (!acpi_table_parse(ACPI_SIG_SRAT, acpi_parse_srat)) {
 		acpi_table_parse_srat(ACPI_SRAT_TYPE_CPU_AFFINITY,
 				      acpi_parse_processor_affinity, NR_CPUS);
+#ifdef CONFIG_HAVE_ARCH_PARSE_SRAT
 		acpi_table_parse_srat(ACPI_SRAT_TYPE_MEMORY_AFFINITY,
 				      acpi_parse_memory_affinity,
 				      NR_NODE_MEMBLKS);
+#endif
 	}
 
 	/* SLIT: System Locality Information Table */

commit aca9de453911d095a9701ee6ebbae7fd3d6c7c1e
Author: Russ Anderson <rja@sgi.com>
Date:   Fri May 16 10:02:06 2008 -0500

    acpi: fix boot breakage on Altix
    
    Signed-off-by: Ingo Molnar <mingo@elte.hu>

diff --git a/arch/ia64/Kconfig b/arch/ia64/Kconfig
index 16be414..1be94eb 100644
--- a/arch/ia64/Kconfig
+++ b/arch/ia64/Kconfig
@@ -60,6 +60,10 @@ config RWSEM_XCHGADD_ALGORITHM
 	bool
 	default y
 
+config HAVE_ARCH_PARSE_SRAT
+	bool
+	default y
+
 config ARCH_HAS_ILOG2_U32
 	bool
 	default n
diff --git a/include/linux/acpi.h b/include/linux/acpi.h
index 41f7ce7..b426ac5 100644
--- a/include/linux/acpi.h
+++ b/include/linux/acpi.h
@@ -93,7 +93,7 @@ int acpi_parse_mcfg (struct acpi_table_header *header);
 void acpi_table_print_madt_entry (struct acpi_subtable_header *madt);
 
 /* the following four functions are architecture-dependent */
-#ifdef CONFIG_HAVE_ARCH_PARSE_SRAT
+#if defined(CONFIG_HAVE_ARCH_PARSE_SRAT) && !defined(NR_NODE_MEMBLKS)
 #define NR_NODE_MEMBLKS MAX_NUMNODES
 #define acpi_numa_slit_init(slit) do {} while (0)
 #define acpi_numa_processor_affinity_init(pa) do {} while (0)

  reply	other threads:[~2008-06-17  6:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-17  3:46 linux-next: x86 tree build failure Stephen Rothwell
2008-06-17  5:58 ` Ingo Molnar
2008-06-17  6:08   ` Ingo Molnar
2008-06-17  6:45     ` Ingo Molnar [this message]
2008-06-18  5:04   ` Stephen Rothwell
2008-06-18  6:39     ` Ingo Molnar
2008-06-25  3:17 ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2008-07-17  2:07 Stephen Rothwell
2008-07-17  9:23 ` Vegard Nossum
2008-07-18 20:10   ` Ingo Molnar
2008-07-18 20:12     ` Ingo Molnar
2008-07-19 12:11       ` Stephen Rothwell
2008-08-25 10:22 Stephen Rothwell
2008-08-25 10:28 ` Ingo Molnar
2008-09-11 23:56 Stephen Rothwell
2008-09-12  6:05 ` Joerg Roedel
2008-09-12  7:31   ` Stephen Rothwell
2008-09-12  7:54     ` Joerg Roedel
2008-09-12  8:30     ` Ingo Molnar
2008-09-14 19:52       ` Stephen Rothwell

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=20080617064559.GA23580@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.