[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1651331541.54386.1476371383378.JavaMail.zimbra@efficios.com>
Date: Thu, 13 Oct 2016 15:09:43 +0000 (UTC)
From: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
lttng-dev <lttng-dev@...ts.lttng.org>,
John Stultz <john.stultz@...aro.org>
Subject: 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 gregkh@...uxfoundation.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
Powered by blists - more mailing lists