From: Andi Kleen <andi@firstfloor.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/7] Simple Performance Counters: x86_64 support
Date: Wed, 1 Aug 2007 20:57:41 +0200 [thread overview]
Message-ID: <20070801185741.GD20713@one.firstfloor.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0708011144450.22867@schroedinger.engr.sgi.com>
On Wed, Aug 01, 2007 at 11:45:39AM -0700, Christoph Lameter wrote:
> On Wed, 1 Aug 2007, Andi Kleen wrote:
>
> > > It is certainly interesting to compare alternative ways of handling the
> > > instruction streams by various processors or models of processors.
> >
> > Well you have to do a lot more work then to handle instable TSCs then.
>
> I have been using this for 2 years. It works fine for my purposes.
That might be on your systems, but for a mainline submission the
standards are higher.
>
> > In particular the frequencies can be different between CPUs, they
> > change (which you can catch with cpufreq notifiers) and during the
> > cpufreq change period they're instable (as in you can't tell for
> > some time which frequency they're currently running at and they
> > might be running immediate frequencies)
>
> Well then simply make sure that they do not change while you measure.
That would be a merge blocker in my opinion. Suitable for local
hacks, but nothing we want in tree.
-Andi
next prev parent reply other threads:[~2007-08-01 18:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 23:25 [PATCH 2/7] Simple Performance Counters: x86_64 support Christoph Lameter
2007-08-01 10:53 ` Andi Kleen
2007-08-01 17:52 ` Christoph Lameter
2007-08-01 18:26 ` Andi Kleen
2007-08-01 18:29 ` Christoph Lameter
2007-08-01 18:40 ` Andi Kleen
2007-08-01 18:45 ` Christoph Lameter
2007-08-01 18:57 ` Andi Kleen [this message]
2007-08-01 18:58 ` Christoph Lameter
2007-08-01 19:15 ` Andi Kleen
2007-08-17 16:10 ` Mathieu Desnoyers
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=20070801185741.GD20713@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.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.