On Tue, 2013-09-24 at 15:27 -0400, Chris Metcalf wrote: > > It's hard to tell with gcc ... the best I've had so far as an option was > > something that would mark my per-cpu register (r13) *itself* as clobbered... > > Well, as I said above, that would be better, but it requires providing an > alternate definition of barrier() that is per-architecture, not just > per-compiler.
My compiler people tell me "clobbered" is wrong. It will tell the compiler that barrier() damages r13 (or whatever other register you use) and instead make it do exactly the wrong thing which is to back it up before the barrier and use the backup :-) I'm told what we need is an empty asm that marks r13 as an *output* (and possible an input as well to be safe). I will experiment. > If there's interest in pursuing a solution like that, it > would be technically somewhat better; in particular, with PREEMPT_NONE, > you could treat the "tp" register int as locally scoped in an inline, and > the compiler wouldn't have to reload it after function calls. Presumably > we'd need to pick an asm header that could provide an arch_barrier_clobbers > string that would be added to barrier() for gcc if it were defined. My idea was to add a preempt_barrier() and put that in preempt_enable/disable and the various irq enable/disable. Cheers, Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
