Re: [RFC v3 2/3] kernel/time/clockevents: make setting of ->mult and ->mult_mono atomic

2016-07-21 Thread John Stultz
On Thu, Jul 21, 2016 at 12:24 PM, Nicolai Stange wrote: > John Stultz writes: > >> On Wed, Jul 13, 2016 at 6:00 AM, Nicolai Stange wrote: >>> In order to avoid races between setting a struct clock_event_device's >>> ->mult_mono

Re: [RFC v3 2/3] kernel/time/clockevents: make setting of ->mult and ->mult_mono atomic

2016-07-21 Thread John Stultz
On Thu, Jul 21, 2016 at 12:24 PM, Nicolai Stange wrote: > John Stultz writes: > >> On Wed, Jul 13, 2016 at 6:00 AM, Nicolai Stange wrote: >>> In order to avoid races between setting a struct clock_event_device's >>> ->mult_mono in clockevents_update_freq() and yet to be implemented updates >>>

Re: [RFC v3 2/3] kernel/time/clockevents: make setting of ->mult and ->mult_mono atomic

2016-07-21 Thread Nicolai Stange
John Stultz writes: > On Wed, Jul 13, 2016 at 6:00 AM, Nicolai Stange wrote: >> In order to avoid races between setting a struct clock_event_device's >> ->mult_mono in clockevents_update_freq() and yet to be implemented updates >> triggered from the

Re: [RFC v3 2/3] kernel/time/clockevents: make setting of ->mult and ->mult_mono atomic

2016-07-21 Thread Nicolai Stange
John Stultz writes: > On Wed, Jul 13, 2016 at 6:00 AM, Nicolai Stange wrote: >> In order to avoid races between setting a struct clock_event_device's >> ->mult_mono in clockevents_update_freq() and yet to be implemented updates >> triggered from the timekeeping core, the setting of ->mult and

Re: [RFC v3 2/3] kernel/time/clockevents: make setting of ->mult and ->mult_mono atomic

2016-07-21 Thread John Stultz
On Wed, Jul 13, 2016 at 6:00 AM, Nicolai Stange wrote: > In order to avoid races between setting a struct clock_event_device's > ->mult_mono in clockevents_update_freq() and yet to be implemented updates > triggered from the timekeeping core, the setting of ->mult and

Re: [RFC v3 2/3] kernel/time/clockevents: make setting of ->mult and ->mult_mono atomic

2016-07-21 Thread John Stultz
On Wed, Jul 13, 2016 at 6:00 AM, Nicolai Stange wrote: > In order to avoid races between setting a struct clock_event_device's > ->mult_mono in clockevents_update_freq() and yet to be implemented updates > triggered from the timekeeping core, the setting of ->mult and ->mult_mono > should be made

[RFC v3 2/3] kernel/time/clockevents: make setting of ->mult and ->mult_mono atomic

2016-07-13 Thread Nicolai Stange
In order to avoid races between setting a struct clock_event_device's ->mult_mono in clockevents_update_freq() and yet to be implemented updates triggered from the timekeeping core, the setting of ->mult and ->mult_mono should be made atomic. Protect the update in clockevents_update_freq() by

[RFC v3 2/3] kernel/time/clockevents: make setting of ->mult and ->mult_mono atomic

2016-07-13 Thread Nicolai Stange
In order to avoid races between setting a struct clock_event_device's ->mult_mono in clockevents_update_freq() and yet to be implemented updates triggered from the timekeeping core, the setting of ->mult and ->mult_mono should be made atomic. Protect the update in clockevents_update_freq() by