* Peter Zijlstra <[email protected]> [150216 05:13]: > From: Thomas Gleixner <[email protected]> > > clockevents_notify() is a leftover from the early design of the > clockevents facility. It's really not a notification mechanism, it's a > multiplex call. We are way better off to have explicit calls instead of this > monstrosity. > > Split out the broadcast control into a separate function and provide > inline helpers. Switch clockevents_notify() over. This will go away > once all callers are converted. > > This also gets rid of the nested locking of clockevents_lock and > broadcast_lock. The broadcast control functions do not require > clockevents_lock. Only the managing functions > (setup/shutdown/suspend/resume of the broadcast device require > clockevents_lock.
Seems to still behave for my off-idle PM tests after a quick try on Peter's timers/core branch. Might be too late, but just in case it's not: Tested-by: Tony Lindgren <[email protected]> -- 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/
