From: Rusty Russell <rusty@rustcorp.com.au>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: schwidefsky@de.ibm.com,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: s390(64) per_cpu in modules (ipv6)
Date: Fri, 15 Oct 2004 11:41:40 +1000 [thread overview]
Message-ID: <1097804500.22673.51.camel@localhost.localdomain> (raw)
In-Reply-To: <20040629233537.523db68c@lembas.zaitcev.lan>
On Wed, 2004-06-30 at 16:35, Pete Zaitcev wrote:
> Hi, Martin,
>
> I tried to build ipv6 as a module in 2.6.7, and it bombs, producing a
> module which wants per_cpu____icmpv6_socket (obviously, undefined).
>
> The problem appears to be caused by this:
>
> #define __get_got_cpu_var(var,offset) \
> (*({ unsigned long *__ptr; \
> asm ( "larl %0,per_cpu__"#var"@GOTENT" : "=a" (__ptr) ); \
> ((typeof(&per_cpu__##var))((*__ptr) + offset)); \
> }))
Heh, I ran into the same problem trying to do this trick for PPC64. You
really need to use __thread and make GCC do the work, AFAICT.
The worse problem is that a (static) per-cpu var declared *inside* a
function gets renamed by gcc; IIRC some generic code used to do this.
Rusty.
--
Anyone who quotes me in their signature is an idiot -- Rusty Russell
next prev parent reply other threads:[~2004-10-15 1:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 6:35 s390(64) per_cpu in modules (ipv6) Pete Zaitcev
2004-06-30 6:45 ` William Lee Irwin III
2004-06-30 6:46 ` Roland Dreier
2004-10-15 1:41 ` Rusty Russell [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-30 13:04 Martin Schwidefsky
2004-06-30 16:07 ` Roland Dreier
2004-06-30 20:55 ` Pete Zaitcev
2004-07-01 13:05 ` Arnd Bergmann
[not found] <OFC25D1557.60BFB654-ON42256F2E.00327ABF-42256F2E.0032D239@de.ibm.com>
2004-10-17 2:51 ` Rusty Russell
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=1097804500.22673.51.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=zaitcev@redhat.com \
/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