[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081106223417.GA26686@x200.localdomain>
Date: Fri, 7 Nov 2008 01:34:17 +0300
From: Alexey Dobriyan <adobriyan@...il.com>
To: Christoph Lameter <cl@...ux-foundation.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
rusty@...tcorp.com.au
Subject: Re: next-20081106: undefined reference to `__per_cpu_start'
On Thu, Nov 06, 2008 at 01:15:07PM -0600, Christoph Lameter wrote:
> On Thu, 6 Nov 2008, Alexey Dobriyan wrote:
>
> > On blackfin-BF526-EZBRD and other blackfins:
> >
> > LD .tmp_vmlinux1
> > mm/built-in.o: In function `cpu_alloc_init':
> > (.init.text+0x1486): undefined reference to `__per_cpu_start'
> > mm/built-in.o: In function `cpu_alloc_init':
> > (.init.text+0x148c): undefined reference to `__per_cpu_start'
> > mm/built-in.o: In function `cpu_alloc_init':
> > (.init.text+0x1492): undefined reference to `__per_cpu_end'
> > mm/built-in.o: In function `cpu_alloc_init':
> > (.init.text+0x1496): undefined reference to `__per_cpu_end'
>
> Any contigencies for __per_cpu_start/end in your blackfin vmlinux.lds.h?
> That is where these symbols are defined
>
> Or did you use generic percpu support and set
> CONFIG_HAVE_ZERO_BASED_PER_CPU?
References are coming from PERCPU_AREA_SIZE.
This works, but I have no idea if this correct:
--- 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)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists