On Wed, 26 Jun 2013, Andi Kleen wrote: > On Wed, Jun 26, 2013 at 05:07:02PM -0400, Waiman Long wrote: > > Looking from the other perspective, we may want the locking code to > > have the same behavior whether spinlock debugging is enabled or not. > > Disabling the optimization will cause the code path to differ which > > may not be what we want. Of course, I can change it if other people > > also think it is the right way to do it. > > Lock debugging already has quite different timing/lock semantics. Locks have no timing related sematics and lock debugging does not change the semantics of locks. Lock debugging adds overhead to the locking functions, but it does not affect the semantics of locks. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
