Fix: bump stable kernel version ranges for clock work-around
authorMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Thu, 13 Oct 2016 13:50:21 +0000 (15:50 +0200)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Thu, 13 Oct 2016 13:57:35 +0000 (15:57 +0200)
commit2bdfbc55e9179be5a184a8c5f7259c90b3e07153
tree346322940c0faf33e7284325af74d6afc8b369df
parente8402061f4d8479b66b41ecbfa00cb68d84cfb6a
Fix: bump stable kernel version ranges for clock work-around

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.

We therefore need to bump the version ranges for the work-around
in lttng-modules.

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
CC: John Stultz <john.stultz@linaro.org>
wrapper/trace-clock.h
This page took 0.025014 seconds and 4 git commands to generate.