- 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
Hi,
These releases simply bump the stable kernel version range checks
to include 4.8.1, 4.7.7, 4.4.24, and 4.1.34 for the kernel tracer
clock source train-wreck work-around.
Greg, if you see this message, please make sure to cherry-pick
Linus' master commit commit 58bfea9532 "timekeeping: Fix
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
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
