[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161121172613.50178540@gandalf.local.home>
Date: Mon, 21 Nov 2016 17:26:13 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Joel Fernandes <joelaf@...gle.com>
Cc: linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
John Stultz <john.stultz@...aro.org>,
Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH v2 2/2] trace: Add an option for boot clock as trace
clock
On Mon, 21 Nov 2016 14:12:50 -0800
Joel Fernandes <joelaf@...gle.com> wrote:
> Unlike monotonic clock, boot clock as a trace clock will account for
> time spent in suspend useful for tracing suspend/resume. This uses
> earlier introduced infrastructure for using the fast boot clock.
>
> Cc: Steven Rostedt <rostedt@...dmis.org>
> Cc: Thomas Gleixner <tglx@...utronix.de>
> Cc: John Stultz <john.stultz@...aro.org>
> Cc: Ingo Molnar <mingo@...hat.com>
> Signed-off-by: Joel Fernandes <joelaf@...gle.com>
> ---
> kernel/trace/trace.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index 8696ce6..f7b64db 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -1125,6 +1125,7 @@ static struct {
> { trace_clock, "perf", 1 },
> { ktime_get_mono_fast_ns, "mono", 1 },
> { ktime_get_raw_fast_ns, "mono_raw", 1 },
> + { ktime_get_boot_fast_ns, "boot", 1 },
> ARCH_TRACE_CLOCKS
> };
>
I'm fine with this change, but can you please update
Documentation/trace/ftrace.txt under trace_clock. I notice that mono
and mono_raw are missing too.
-- Steve
Powered by blists - more mailing lists