From: Christoph Lameter <cl@linux-foundation•org>
To: Alexey Dobriyan <adobriyan@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
rusty@rustcorp•com.au
Subject: Re: next-20081106: undefined reference to `__per_cpu_start'
Date: Fri, 7 Nov 2008 12:32:53 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.64.0811071229450.5387@quilx.com> (raw)
In-Reply-To: <20081106223417.GA26686@x200.localdomain>
On Fri, 7 Nov 2008, Alexey Dobriyan wrote:
> --- a/include/linux/percpu.h
> +++ b/include/linux/percpu.h
> @@ -51,6 +51,8 @@
> #define DEFINE_PER_CPU_FIRST(type, name) \
> DEFINE_PER_CPU(type, name)
>
> +#define PERCPU_AREA_SIZE 0
> +
> #endif /* !CONFIG_SMP */
>
> #define EXPORT_PER_CPU_SYMBOL(var) EXPORT_SYMBOL(per_cpu__##var)
No we need a percpu allocation area even on UP.
next prev parent reply other threads:[~2008-11-07 18:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 6:36 linux-next: Tree for November 6 Stephen Rothwell
2008-11-06 18:39 ` next-20081106: undefined reference to `__per_cpu_start' Alexey Dobriyan
2008-11-06 19:15 ` Christoph Lameter
2008-11-06 22:34 ` Alexey Dobriyan
2008-11-07 18:32 ` Christoph Lameter [this message]
2008-11-07 5:21 ` Stephen Rothwell
2008-11-07 5:44 ` Alexey Dobriyan
2008-11-07 18:28 ` Christoph Lameter
2008-11-07 18:40 ` Christoph Lameter
2008-11-18 4:33 ` linux-next: cpu_alloc tree patch (Was: Re: next-20081106: undefined reference to `__per_cpu_start') Stephen Rothwell
2008-11-19 19:18 ` Christoph Lameter
2008-11-12 7:59 ` next-20081106: undefined reference to `__per_cpu_start' Geert Uytterhoeven
2008-11-12 11:18 ` Mike Frysinger
2008-11-06 18:54 ` next-20081106: perfmon on ia64 Alexey Dobriyan
2008-11-06 20:44 ` stephane eranian
2008-11-06 19:44 ` next-20081106: today's ftrace episode Alexey Dobriyan
2008-11-06 20:03 ` Steven Rostedt
2008-11-06 20:15 ` Alexey Dobriyan
2008-11-06 20:28 ` Steven Rostedt
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=Pine.LNX.4.64.0811071229450.5387@quilx.com \
--to=cl@linux-foundation$(echo .)org \
--cc=adobriyan@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rusty@rustcorp$(echo .)com.au \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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