From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] x86: cleanup early per cpu variables/accesses v3-folded
Date: Tue, 22 Apr 2008 08:09:12 -0700 [thread overview]
Message-ID: <480DFF98.7030203@sgi.com> (raw)
In-Reply-To: <20080422135944.GA24966@elte.hu>
Ingo Molnar wrote:
> * Mike Travis <travis@sgi.com> wrote:
>
>> * Introduce a new PER_CPU macro called "EARLY_PER_CPU". This is
>> used by some per_cpu variables that are initialized and accessed
>> before there are per_cpu areas allocated.
>
> build fails with:
>
> arch/x86/kernel/built-in.o: In function `flat_apic_id_registered':
> genapic_flat_64.c:(.text+0x13e1d): undefined reference to `phys_cpu_present_map'
> genapic_flat_64.c:(.text+0x13e24): undefined reference to `phys_cpu_present_map'
> arch/x86/kernel/built-in.o: In function `APIC_init_uniprocessor':
> : undefined reference to `phys_cpu_present_map'
> [...]
>
> with this config:
>
> http://redhat.com/~mingo/misc/config-Tue_Apr_22_15_40_10_CEST_2008.bad
>
> Ingo
Ok, thanks, I'll check it out.
Mike
next prev parent reply other threads:[~2008-04-22 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 1:34 [PATCH 0/4] x86: cleanup early per cpu variables/accesses v3-folded Mike Travis
2008-04-22 1:34 ` [PATCH 1/4] " Mike Travis
2008-04-22 13:59 ` Ingo Molnar
2008-04-22 15:09 ` Mike Travis [this message]
2008-04-22 16:24 ` Mike Travis
2008-04-22 1:34 ` [PATCH 2/4] x86: restore pda nodenumber field Mike Travis
2008-04-22 1:34 ` [PATCH 3/4] x86: remove the 256k node_to_cpumask_map after init Mike Travis
2008-04-22 1:34 ` [PATCH 4/4] sched: replace MAX_NUMNODES with nr_node_ids in kernel/sched.c Mike Travis
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=480DFF98.7030203@sgi.com \
--to=travis@sgi.com \
--cc=akpm@linux-foundation.org \
--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 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.