From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Drew Richardson <drew.richardson@arm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
John Stultz <john.stultz@linaro.org>,
Wade Cherry <wade.cherry@arm.com>
Subject: Re: [PATCH] ftrace: Provide trace clock monotonic raw
Date: Mon, 4 May 2015 15:10:05 +0000 (UTC) [thread overview]
Message-ID: <199091314.42407.1430752205090.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <1430750469-16428-1-git-send-email-drew.richardson@arm.com>
----- Original Message -----
> Expose the NMI safe accessor to the monotonic raw clock to the
> tracer. The mono clock was added with commit
> 1b3e5c0936046e7e023149ddc8946d21c2ea20eb. Although the monotonic raw
> clock cannot be used to compare time between different machines, it is
> not perterbed by ntp.
perterbed -> perturbed
>
> Signed-off-by: Drew Richardson <drew.richardson@arm.com>
>
What is the use-case that justify exposing the "raw fast"
clock that cannot be handled by the "monotonic fast" clock ?
Thanks,
Mathieu
> ---
> kernel/trace/trace.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index 05330494a0df..458031c31a37 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -876,6 +876,7 @@ static struct {
> { trace_clock_jiffies, "uptime", 0 },
> { trace_clock, "perf", 1 },
> { ktime_get_mono_fast_ns, "mono", 1 },
> + { ktime_get_raw_fast_ns, "mono_raw", 1 },
> ARCH_TRACE_CLOCKS
> };
>
> --
> 2.1.4
>
>
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2015-05-04 15:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 14:41 [PATCH] ftrace: Provide trace clock monotonic raw Drew Richardson
2015-05-04 15:10 ` Mathieu Desnoyers [this message]
2015-05-04 20:05 ` Drew Richardson
2015-05-04 20:47 ` John Stultz
2015-05-04 20:57 ` Peter Zijlstra
2015-05-05 14:54 ` Drew Richardson
2015-05-08 0:42 ` Steven Rostedt
2015-05-08 1:27 ` Mathieu Desnoyers
2015-05-08 14:09 ` Steven Rostedt
2015-05-08 14:29 ` Drew Richardson
2015-05-08 14:30 ` [PATCHv3] " Drew Richardson
2015-05-08 14:41 ` Steven Rostedt
2015-05-08 16:05 ` John Stultz
2015-05-08 16:15 ` Steven Rostedt
2015-05-08 16:21 ` John Stultz
2015-05-08 16:11 ` Peter Zijlstra
2015-05-12 14:26 ` Thomas Gleixner
2015-05-12 19:59 ` Steven Rostedt
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=199091314.42407.1430752205090.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=drew.richardson@arm.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=wade.cherry@arm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox