From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
Steven Rostedt <srostedt@redhat.com>
Subject: Re: [PATCH 1/2] ftrace: single CPU tracers use CPU clock
Date: Sat, 26 Jul 2008 14:40:58 +0200 [thread overview]
Message-ID: <20080726124058.GD20713@elte.hu> (raw)
In-Reply-To: <20080725220334.781928198@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> The current ftrace clock uses the sched_clock.c code. This code tries
> to handle cases where the TSC is out of sync between different CPUs.
> Unfortunately, even with insync TSCs, due to drifts between the CPU
> clock and the GTOD clock, we might get some inaccuracy in a single CPU
> trace.
>
> Some tracers (irqsoff, preemptoff, preempirqsoff) only care about a
> trace on a single CPU. This patch changes the ftrace_now (the clock
> reader) from a function call to a function variable. On initialization
> of a tracer, the tracer will be allowed to choose which type of clock
> to use.
>
> Now the irqsoff, preemptoff and preemptirqs off tracers can have
> accurate traces with the local CPU clock without affecting the tracers
> that want the modified clock that tries to keep the different CPU
> clock reads in sync.
this is not a good idea. We want to fix cpu_clock(), not work around any
deficiencies it might have.
Ingo
next prev parent reply other threads:[~2008-07-26 12:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 22:00 [PATCH 0/2] ftrace minor updates Steven Rostedt
2008-07-25 22:00 ` [PATCH 1/2] ftrace: single CPU tracers use CPU clock Steven Rostedt
2008-07-26 12:40 ` Ingo Molnar [this message]
2008-07-26 13:15 ` Steven Rostedt
2008-07-26 13:21 ` Ingo Molnar
2008-07-26 15:03 ` Steven Rostedt
2008-07-26 15:26 ` Ingo Molnar
2008-07-26 18:23 ` Steven Rostedt
2008-07-25 22:00 ` [PATCH 2/2] ftrace: disable tracing on acpi idle calls Steven Rostedt
2008-07-26 12:42 ` Ingo Molnar
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=20080726124058.GD20713@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@osdl.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.