lkml.org 
[lkml]   [2014]   [Jul]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch 54/55] timekeeping: Provide fast and NMI safe access to CLOCK_MONOTONIC[_RAW]
On Mon, 14 Jul 2014, Mathieu Desnoyers wrote:

> ----- Original Message -----
> > From: "Peter Zijlstra" <peterz@infradead.org>
> > To: "Thomas Gleixner" <tglx@linutronix.de>
> > Cc: "LKML" <linux-kernel@vger.kernel.org>, "John Stultz" <john.stultz@linaro.org>, "Steven Rostedt"
> > <rostedt@goodmis.org>, "Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>
> > Sent: Monday, July 14, 2014 5:47:50 AM
> > Subject: Re: [patch 54/55] timekeeping: Provide fast and NMI safe access to CLOCK_MONOTONIC[_RAW]
> >
> > On Fri, Jul 11, 2014 at 01:45:19PM -0000, Thomas Gleixner wrote:
> > > +static struct tk_fast tk_fast_raw ____cacheline_aligned;
> > > +static struct tk_fast tk_fast_mono ____cacheline_aligned;
> >
> > Question to the 'trace maniacs'; why do you lot need access to mono_raw?
> >
> > I would much prefer to limit choice here.
>
> For LTTng, which I guess qualifies as bring part of the aforementioned
> trace maniacs group, we only need the "tk_fast_mono" clock. We don't
> need mono_raw.
>
> We can then correlate with user-space traces by using tk_fast_mono in
> kernel-space and using CLOCK_MONOTONIC in userspace.

I'm happy to ditch the raw one ...


\
 
 \ /
  Last update: 2014-07-14 20:41    [W:0.438 / U:0.176 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site