From: Adrian Bunk <bunk@kernel.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Alexey Starikovskiy <astarikovskiy@suse.de>,
tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: Voyager phys_cpu_present_map compile error
Date: Fri, 25 Apr 2008 19:17:45 +0300 [thread overview]
Message-ID: <20080425161745.GA21168@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <1209135044.3087.3.camel@localhost.localdomain>
On Fri, Apr 25, 2008 at 09:50:43AM -0500, James Bottomley wrote:
> On Mon, 2008-04-21 at 22:14 +0200, Ingo Molnar wrote:
> > * Adrian Bunk <bunk@kernel.org> wrote:
> >
> > > > +#ifndef CONFIG_X86_VOYAGER
> > > > /* Bitmask of physically existing CPUs */
> > > > physid_mask_t phys_cpu_present_map;
> > > > +#endif
> > > >...
> > >
> > > Alexey noted that phys_cpu_present_map for Voyager and !Voyager also
> > > have different types and suggested to make the Voyager one static
> > > instead (additional renaming of the Voyager one also makes sense).
> >
> > yep, done by the patch below.
>
> Actually, this isn't the right patch. The point is not to avoid the
> symbol clash, it's to let voyager identify correctly that you have a
> leaking symbol. In this case phys_cpu_present_map is exposed outside of
> SMP. The correct fix (and one which sweeps op other storage for
> unnecessary symbols is this):
>
> James
>
> ---
>
> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
> index c0c68c1..d68aa53 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 CONIFG_X86_SMP
>...
tpyo ;)
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-04-25 16:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 0:02 Adrian Bunk
2008-04-21 8:53 ` Adrian Bunk
2008-04-21 12:00 ` Ingo Molnar
2008-04-21 12:55 ` H. Peter Anvin
2008-04-21 14:10 ` Status of SGI 320/540 (Visual Workstation) support? Adrian Bunk
2008-04-22 6:19 ` Andrey Panin
2008-04-22 13:29 ` Voyager phys_cpu_present_map compile error Andrew Morton
2008-04-22 15:25 ` Andy Whitcroft
2008-04-21 13:00 ` H. Peter Anvin
2008-04-21 15:42 ` James Bottomley
2008-04-21 20:03 ` Ingo Molnar
2008-04-21 23:08 ` James Bottomley
2008-04-21 19:55 ` Ingo Molnar
2008-04-21 20:03 ` H. Peter Anvin
2008-04-21 20:11 ` Ingo Molnar
2008-04-21 20:10 ` H. Peter Anvin
2008-04-23 8:53 ` Pavel Machek
2008-04-21 13:27 ` Adrian Bunk
2008-04-21 20:14 ` Ingo Molnar
2008-04-21 21:57 ` James Bottomley
2008-04-25 14:50 ` James Bottomley
2008-04-25 16:17 ` Adrian Bunk [this message]
2008-04-25 16:33 ` James Bottomley
2008-04-28 17:59 ` Ingo Molnar
2008-04-28 19:09 ` James Bottomley
2008-04-21 15:58 ` James Bottomley
2008-04-21 19:51 ` Ingo Molnar
2008-04-21 20:09 ` Adrian Bunk
2008-04-21 20:13 ` Ingo Molnar
2008-04-21 20:26 ` Adrian Bunk
2008-04-21 20:29 ` Ingo Molnar
2008-04-21 21:02 ` Adrian Bunk
2008-04-21 22:31 ` Ingo Molnar
2008-04-26 7:43 ` Pavel Machek
2008-04-27 0:44 ` H. Peter Anvin
2008-04-27 1:06 ` Adrian Bunk
2008-04-27 1:45 ` H. Peter Anvin
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=20080425161745.GA21168@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--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 \
/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
all inboxes | Powered by JetHome®