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>,
john stultz <johnstul@us.ibm.com>,
linux-kernel@vger.kernel.org,
Dmitry Adamushko <dmitry.adamushko@gmail.com>
Subject: Re: [PATCH 0/3] [PATCH] more sched_clock updates
Date: Fri, 11 Jul 2008 15:56:30 +0200 [thread overview]
Message-ID: <20080711135630.GD32159@elte.hu> (raw)
In-Reply-To: <20080709041530.668120406@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> ftrace is still seeing jumps in the sched_clock.c code that is not
> seen in using sched_clock() function itself. The following patches fix
> some of the issues that I've seen. There is still a slight drift but
> all my attempts to remove it completely have failed. Patch 3 does the
> best sofar at keeping the jumps to a minimum.
cool stuff! I've created a new -tip topic branch for your sched-clock
fixes and enhancements, under tip/sched/clock, and have picked up your
patches:
Steven Rostedt (7):
sched_clock: record from last tick
sched_clock: widen the max and min time
sched_clock: stop maximum check on NO HZ
sched_clock: fix calculation of other CPU
sched_clock: only update deltas with local reads.
sched_clock: record TSC after gtod
sched_clock: and multiplier for TSC to gtod drift
thanks,
Ingo
prev parent reply other threads:[~2008-07-11 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 4:15 [PATCH 0/3] [PATCH] more sched_clock updates Steven Rostedt
2008-07-09 4:15 ` [PATCH 1/3] sched_clock: only update deltas with local reads Steven Rostedt
2008-07-09 4:15 ` [PATCH 2/3] sched_clock: record TSC after gtod Steven Rostedt
2008-07-09 4:15 ` [PATCH 3/3] sched_clock: and multiplier for TSC to gtod drift Steven Rostedt
2008-07-11 13:56 ` Ingo Molnar [this message]
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=20080711135630.GD32159@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=dmitry.adamushko@gmail.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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