Re: [PATCH lttng-modules] Fix: bump stable kernel version ranges for clock work-around
- On Oct 13, 2016, at 5:00 PM, Greg Kroah-Hartman gre...@linuxfoundation.org wrote: > On Thu, Oct 13, 2016 at 03:56:55PM +0200, Mathieu Desnoyers wrote: >> Linux commit 27727df240c7 ("Avoid taking lock in NMI path with >> CONFIG_DEBUG_TIMEKEEPING"), changed the logic to open-code >> the timekeeping_get_ns() function, but forgot to include >> the unit conversion from cycles to nanoseconds, breaking the >> function's output, which impacts LTTng. >> >> We expected Linux commit 58bfea9532 "timekeeping: Fix >> __ktime_get_fast_ns() regression" to make its way into stable >> kernels promptly, but it appears new stable kernel releases were >> done before the fix was cherry-picked from the master branch. > > Sorry, will go queue that up now... Thanks Greg! :) Mathieu -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com
Re: [PATCH lttng-modules] Fix: bump stable kernel version ranges for clock work-around
On Thu, Oct 13, 2016 at 03:56:55PM +0200, Mathieu Desnoyers wrote: > Linux commit 27727df240c7 ("Avoid taking lock in NMI path with > CONFIG_DEBUG_TIMEKEEPING"), changed the logic to open-code > the timekeeping_get_ns() function, but forgot to include > the unit conversion from cycles to nanoseconds, breaking the > function's output, which impacts LTTng. > > We expected Linux commit 58bfea9532 "timekeeping: Fix > __ktime_get_fast_ns() regression" to make its way into stable > kernels promptly, but it appears new stable kernel releases were > done before the fix was cherry-picked from the master branch. Sorry, will go queue that up now... greg k-h