From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
lttng-dev <lttng-dev@lists.lttng.org>,
John Stultz <john.stultz@linaro.org>
Subject: Re: [PATCH lttng-modules] Fix: bump stable kernel version ranges for clock work-around
Date: Thu, 13 Oct 2016 15:09:43 +0000 (UTC) [thread overview]
Message-ID: <1651331541.54386.1476371383378.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <20161013150036.GA21105@kroah.com>
----- On Oct 13, 2016, at 5:00 PM, Greg Kroah-Hartman gregkh@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
next prev parent reply other threads:[~2016-10-13 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 13:56 [PATCH lttng-modules] Fix: bump stable kernel version ranges for clock work-around Mathieu Desnoyers
2016-10-13 15:00 ` Greg Kroah-Hartman
2016-10-13 15:09 ` Mathieu Desnoyers
2016-10-13 15:09 ` Mathieu Desnoyers [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-13 13:56 Mathieu Desnoyers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1651331541.54386.1476371383378.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lttng-dev@lists.lttng.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.