On Tue, Mar 24, 2015 at 08:20:07AM -0700, John Stultz wrote: > On Thu, Mar 19, 2015 at 2:31 AM, Peter Zijlstra <[email protected]> wrote: > > Hi John, > > > > So yeah, I just didn't try hard enough it seems; how about this? > > Yea, this looks much better! I'll queue it up for testing and if that > goes well include it for 4.1.
I have a few patches that depend on it, so if you're ok with it I'd like to carry the lot. But yes please test ;-) > > Also, I think we should double check that everything passed to > > tk_setup_internals(.clock) is either static storage or RCU-sched freed, > > because with the whole latch thing one CPUs (fast) access might still be > > in progress while the other is freeing the clock struct. > > > > Not sure what the lifetime rules of struct clocksource are here. > > At one point it was install and never remove, but I think Thomas > changed that awhile back, so I think your concern here is a good one. OK, I'll try and dig around a bit on this. -- 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/
