public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: WANG Cong <xiyou.wangcong@gmail.com>,
	toralf.foerster@gmx.de, linux-kernel@vger.kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Mike Travis <travis@sgi.com>,
	Alexey Starikovskiy <astarikovskiy@suse.de>
Subject: Re: build issue #380 for v2.6.26-rc1-279-g28a4acb : mach-voyager: multiple definition of `phys_cpu_present_map'
Date: Sat, 10 May 2008 09:01:48 -0500	[thread overview]
Message-ID: <1210428108.4002.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20080510131752.GA888@elte.hu>

On Sat, 2008-05-10 at 15:17 +0200, Ingo Molnar wrote:
> * Ingo Molnar <mingo@elte.hu> wrote:
> 
> > > I already told you that this was incorrect.  This is what I sent as 
> > > the replacement on 28 April and I didn't hear back from you.
> > > 
> > > http://marc.info/?l=linux-kernel&m=120941111400620
> > 
> > ok - picked it up for testing - could you please send a signoff line 
> > as well?
> 
> Alexey, the patch from James failed in testing on visws:
> 
>  arch/x86/kernel/built-in.o: In function `init_apic_mappings':
>  : undefined reference to `boot_cpu_physical_apicid'
>  arch/x86/kernel/built-in.o: In function `init_apic_mappings':
>  : undefined reference to `boot_cpu_physical_apicid'
>  arch/x86/kernel/built-in.o: In function `APIC_init_uniprocessor':
>  : undefined reference to `boot_cpu_physical_apicid'
>  arch/x86/kernel/built-in.o: In function `APIC_init_uniprocessor':
> 
> config is at:
> 
>   http://redhat.com/~mingo/misc/config-Sat_May_10_15_05_47_CEST_2008.bad

OK, so these symbols are required on visws as well.  So that makes the
gating config symbol X86_LOCAL_APIC.

Could you run this through the same config to verify; thanks!

James

---

From: James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: [VOYAGER] fix duplicate phys_cpu_present_map symbol

The phys_cpu_present_map is an expected symbol in the SMP harness.
Unfortunately, x86 recently moved this and a few others to
kernel/setup.c where it doesn't quite work because voyager has to
define its own.  Use CONFIG_X86_LOCAL_APIC to isolate these
definitions and fix up another area in setup.c where CONFIG_X86_SMP
should be used instead of CONFIG_SMP.

Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
---
 arch/x86/kernel/setup.c |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index cc6f5eb..3f1f642 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -12,6 +12,7 @@
 #include <asm/mpspec.h>
 #include <asm/apicdef.h>
 
+#ifdef CONFIG_X86_LOCAL_APIC
 unsigned int num_processors;
 unsigned disabled_cpus __cpuinitdata;
 /* Processor that is doing the boot up */
@@ -23,8 +24,9 @@ EXPORT_PER_CPU_SYMBOL(x86_cpu_to_apicid);
 
 /* Bitmask of physically existing CPUs */
 physid_mask_t phys_cpu_present_map;
+#endif
 
-#if defined(CONFIG_HAVE_SETUP_PER_CPU_AREA) && defined(CONFIG_SMP)
+#if defined(CONFIG_HAVE_SETUP_PER_CPU_AREA) && defined(CONFIG_X86_SMP)
 /*
  * Copy data used in early init routines from the initial arrays to the
  * per cpu data areas.  These arrays then become expendable and the
-- 
1.5.4.4




  reply	other threads:[~2008-05-10 14:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09  9:13 build issue #380 for v2.6.26-rc1-279-g28a4acb : mach-voyager: multiple definition of `phys_cpu_present_map' Toralf Förster
2008-05-09  9:30 ` WANG Cong
2008-05-09  9:58   ` Toralf Förster
2008-05-09 10:16     ` WANG Cong
2008-05-09  9:52 ` WANG Cong
2008-05-09  9:58   ` Ingo Molnar
2008-05-09 10:09     ` WANG Cong
2008-05-09 10:59     ` Toralf Förster
2008-05-09 11:22       ` WANG Cong
2008-05-09 14:22     ` James Bottomley
2008-05-09 14:47       ` Ingo Molnar
2008-05-09 15:01         ` Alexey Starikovskiy
2008-05-10 13:17         ` Ingo Molnar
2008-05-10 14:01           ` James Bottomley [this message]
2008-05-10 14:21             ` James Bottomley
2008-05-10 14:34             ` WANG Cong

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=1210428108.4002.5.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=astarikovskiy@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=toralf.foerster@gmx.de \
    --cc=travis@sgi.com \
    --cc=xiyou.wangcong@gmail.com \
    /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