From: "David S. Miller" <davem@davemloft.net>
To: paulus@samba.org
Cc: rth@twiddle.net, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables
Date: Wed, 10 May 2006 15:25:02 -0700 (PDT) [thread overview]
Message-ID: <20060510.152502.11682204.davem@davemloft.net> (raw)
In-Reply-To: <17506.21908.857189.645889@cargo.ozlabs.ibm.com>
From: Paul Mackerras <paulus@samba.org>
Date: Thu, 11 May 2006 07:05:24 +1000
> No, Richard has a point, it's not the value that is the concern, it's
> the address, which gcc could assume is still valid after a barrier.
> Drat.
Oh right, and that's currently part of why we obfuscate the
address computation with the RELOC_HIDE() buisness.
Once we expose what's really going on with something like
__thread, gcc can now be "smart" about it.
next prev parent reply other threads:[~2006-05-10 22:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 4:03 [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables Paul Mackerras
2006-05-10 5:16 ` Olof Johansson
2006-05-10 5:35 ` Alan Modra
2006-05-10 6:22 ` David S. Miller
2006-05-10 6:29 ` Paul Mackerras
2006-05-10 6:39 ` David S. Miller
2006-05-10 7:21 ` Benjamin Herrenschmidt
2006-05-10 10:14 ` David Howells
2006-05-10 7:41 ` Paul Mackerras
2006-05-10 15:47 ` Richard Henderson
2006-05-10 18:04 ` Steven Rostedt
2006-05-10 19:40 ` David S. Miller
2006-05-10 21:05 ` Paul Mackerras
2006-05-10 22:25 ` David S. Miller [this message]
2006-05-10 23:17 ` Segher Boessenkool
2006-05-11 0:22 ` Richard Henderson
2006-05-11 23:41 ` Segher Boessenkool
2006-05-11 1:04 ` Alan Modra
2006-05-11 1:21 ` Paul Mackerras
2006-05-11 2:01 ` Alan Modra
2006-05-11 23:42 ` Segher Boessenkool
2006-05-10 23:05 ` Paul Mackerras
2006-05-10 23:44 ` Paul Mackerras
2006-05-11 0:11 ` David S. Miller
2006-05-18 23:50 ` Paul Mackerras
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=20060510.152502.11682204.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=rth@twiddle.net \
/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