From: WANG Cong <xiyou.wangcong@gmail.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Ingo Molnar <mingo@elte.hu>, 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 22:34:33 +0800 [thread overview]
Message-ID: <20080510143433.GD3148@hacking> (raw)
In-Reply-To: <1210428108.4002.5.camel@localhost.localdomain>
On Sat, May 10, 2008 at 09:01:48AM -0500, James Bottomley wrote:
>
>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.
>
Hmmm, I rechecked the files used 'phys_cpu_present_map'.
$ grep -nr "mpspec.h" arch/x86/ | cut -d: -f 1 | xargs grep "phys_cpu_present_map" | cut -d: -f 1 | uniq
arch/x86/kernel/setup.c
arch/x86/kernel/apic_64.c
arch/x86/kernel/apic_32.c
And in Makefile:
obj-$(CONFIG_X86_LOCAL_APIC) += apic_$(BITS).o nmi_$(BITS).o
So your patch looks correct!
Thanks.
Cong
prev parent reply other threads:[~2008-05-10 14:36 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
2008-05-10 14:21 ` James Bottomley
2008-05-10 14:34 ` WANG Cong [this message]
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=20080510143433.GD3148@hacking \
--to=xiyou.wangcong@gmail.com \
--cc=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 \
/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