Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables

On Thu, May 11, 2006 at 07:05:24AM +1000, Paul Mackerras wrote:
> 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.

That may never happen, at least with a compiler that knows how to
optimise away the addi.  You're using -mtls-size=16 so all your accesses
should look like

	lwz rn,per_cpu_var@tprel(13)

gcc shouldn't think there is any reason to cache the address.

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables
  - From: Paul Mackerras <[email protected]>

References:
- [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables
  - From: Paul Mackerras <[email protected]>
- Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables
  - From: Richard Henderson <[email protected]>
- Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables
  - From: "David S. Miller" <[email protected]>
- Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables
  - From: Paul Mackerras <[email protected]>

Prev by Date: Re: 2.6.16-rtXYZ hangs at boot on quad Opteron
Next by Date: Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables
Previous by thread: Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables
Next by thread: Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]