public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	johnstul@us.ibm.com, mingo@elte.hu, Jiri Bohac <jbohac@suse.cz>
Subject: Re: [PATCH 2/2] i386: sched_clock() follows percpu frequency changes
Date: Sat, 12 May 2007 20:58:35 +0200	[thread overview]
Message-ID: <200705122058.35387.ak@suse.de> (raw)
In-Reply-To: <20070512154408.223236808@mvista.com>

On Saturday 12 May 2007 17:43:46 Daniel Walker wrote:
> Considering that Andi has a similar patch, I'm going to assume there
> is already justification for this..

I just have a patch for sched_clock, which is somewhat different.

> What it ends up doing is allows the TSC to be used in cases which
> we didn't use it before, and hope it's still mostly accurate.

Yes the current code is badly broken in this regard. e.g. i always
hated that it always falls back on powernow systems.

Jiri will hopefully repost his true per CPU TSC patch soon, that should
make it all obsolete.

-Andi

  reply	other threads:[~2007-05-12 18:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12 15:43 [PATCH 1/2] non-string based tsc unstable reasons Daniel Walker
2007-05-12 15:43 ` [PATCH 2/2] i386: sched_clock() follows percpu frequency changes Daniel Walker
2007-05-12 18:58   ` Andi Kleen [this message]
2007-05-12 19:25     ` Daniel Walker
2007-05-12 18:56 ` [PATCH 1/2] non-string based tsc unstable reasons Andi Kleen
2007-05-12 19:10   ` Daniel Walker

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=200705122058.35387.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=dwalker@mvista.com \
    --cc=jbohac@suse.cz \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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