Messages in this thread | | | From | Segher Boessenkool <> | Subject | Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables | Date | Thu, 11 May 2006 01:17:50 +0200 |
| |
>>> How do you plan to address the compiler optimizing >> ... >>> Across the schedule, we may have changed cpus, making the cached >>> address invalid. >> >> Per-cpu variables need to be accessed only with preemption >> disabled. And the preemption enable/disable operations >> provide a compiler memory barrier. > > 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.
Would an asm clobber of GPR13 in the schedule routines (or a wrapper for them, or whatever) work?
Segher
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |