From: Richard Henderson <rth@twiddle.net>
To: Andrew Morton <akpm@osdl.org>
Cc: davidm@hpl.hp.com, arnd@arndb.de, rusty@rustcorp.com.au,
linux-arch@vger.kernel.org, epasch@de.ibm.com, hare@suse.de
Subject: Re: static DEFINE_PER_CPU vs. modules
Date: Tue, 4 May 2004 20:18:33 -0700 [thread overview]
Message-ID: <20040505031833.GA17341@twiddle.net> (raw)
In-Reply-To: <20040504120317.36d45341.akpm@osdl.org>
On Tue, May 04, 2004 at 12:03:17PM -0700, Andrew Morton wrote:
> We can certainly live with this workaround, but it would be nice to find
> something better. per-module per-cpu data sections?
I would think it should be possible to work around the amd64
compiler memory model thing by using inline assembly to access
the movabsq instruction and thense the 64-bit relocation.
r~
next prev parent reply other threads:[~2004-05-05 3:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 15:41 static DEFINE_PER_CPU vs. modules Arnd Bergmann
2004-05-03 17:50 ` David Mosberger
2004-05-03 18:01 ` Richard Henderson
2004-05-03 18:37 ` David Mosberger
2004-05-03 22:24 ` Arnd Bergmann
2004-05-03 23:12 ` David Mosberger
2004-05-04 8:56 ` Arnd Bergmann
2004-05-04 2:38 ` Andrew Morton
2004-05-04 14:17 ` Arnd Bergmann
2004-05-04 16:29 ` David Mosberger
2004-05-04 19:03 ` Andrew Morton
2004-05-04 19:15 ` David Mosberger
2004-05-04 19:23 ` Andrew Morton
2004-05-04 19:45 ` David Mosberger
2004-05-05 8:21 ` Arnd Bergmann
2004-05-05 8:29 ` Andrew Morton
2004-05-05 9:24 ` Arnd Bergmann
2004-05-05 9:33 ` Rusty Russell
2004-05-05 16:17 ` David Mosberger
2004-05-05 3:18 ` Richard Henderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-05 17:42 Martin Schwidefsky
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=20040505031833.GA17341@twiddle.net \
--to=rth@twiddle.net \
--cc=akpm@osdl.org \
--cc=arnd@arndb.de \
--cc=davidm@hpl.hp.com \
--cc=epasch@de.ibm.com \
--cc=hare@suse.de \
--cc=linux-arch@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.