From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christoph Lameter <cl@linux-foundation•org>
Cc: Alexey Dobriyan <adobriyan@gmail•com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
rusty@rustcorp•com.au, Haavard Skinnemoen <hskinnemoen@atmel•com>
Subject: linux-next: cpu_alloc tree patch (Was: Re: next-20081106: undefined reference to `__per_cpu_start')
Date: Tue, 18 Nov 2008 15:33:46 +1100 [thread overview]
Message-ID: <20081118153346.62bf9c11.sfr@canb.auug.org.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0811071235040.5387@quilx.com>
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
Hi Christoph,
On Fri, 7 Nov 2008 12:40:17 -0600 (CST) Christoph Lameter <cl@linux-foundation•org> wrote:
>
> All of these have no invocation of the PERCPU macro from
> asm-generic/vmlinus.lds.h in their arch vmlinux.lds.S. Thus the symbols
> are missing. They are kind of irrelevant since we are only interested in
> the difference between those...
>
> Either we add the PERCPU() macro invocations to each arches vmlinux.lds.S
> file or we need to special case each time __per_cpu_end/__start is used.
> The only use added for the cpu allocator is in include/linux/percpu.h
>
> Make it conditional on CONFIG_SMP
>
> Signed-off-by: Christoph Lameter <cl@linux-foundation•org>
I have applied this to linux-next today. It is not clear to me if this
is a fix for the cpu_alloc tree or the zero-based per_cpu area patches or
a combination of both. If the first, please apply this to the cpu_alloc
tree or I will have to drop the tree. Otherwise, let me know where it
belongs.
Also, considering the "discussions" between Rusty and yourself, I may
need to drop the cpu_alloc tree until they are resolved.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-11-18 4:34 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
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 ` Stephen Rothwell [this message]
2008-11-19 19:18 ` linux-next: cpu_alloc tree patch (Was: Re: next-20081106: undefined reference to `__per_cpu_start') 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=20081118153346.62bf9c11.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=adobriyan@gmail$(echo .)com \
--cc=cl@linux-foundation$(echo .)org \
--cc=hskinnemoen@atmel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rusty@rustcorp$(echo .)com.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