From: Andi Kleen <ak@suse.de>
To: eranian@hpl.hp.com
Cc: linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: [PATCH 18/18] 2.6.17.9 perfmon2 patch for review: new x86_64 files
Date: Wed, 23 Aug 2006 15:44:26 +0200 [thread overview]
Message-ID: <200608231544.26756.ak@suse.de> (raw)
In-Reply-To: <20060823125843.GF697@frankl.hpl.hp.com>
> If they have variations it could be with
> the low power (laptop) models where counters may not be present at all.
It would surprise me if they ever released anything again with no counters.
It's mainly simulators where the counters are missing (e.g. SimNow is a pretty
accurate simulation otherwise, but doesn't have performance counters)
>
> > Perhaps add a force argument again that disables the family check too.
> >
> > > Ok, I think I understand now:
> > > 1/ Bios and Kernel Developer Guide from Ahtlon64 and Opteron 64 is
> > > what you are talking about with K7/K8
> >
> > Well K8.
> >
> > K7 has a different one. But ok. I think you don't try to support K7 at all
> > currently (it has the same register format as K8, but the list of counters
> > is different)
> >
> What is the "commercial name" of K7 processors?
Athlon/Athlon XP/Athlon MP/Sempron (early models, later are K8)/Duron and some
of the Geodes are K7 based too.
-Andi
next prev parent reply other threads:[~2006-08-23 13:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 8:06 [PATCH 18/18] 2.6.17.9 perfmon2 patch for review: new x86_64 files Stephane Eranian
2006-08-23 10:19 ` Andi Kleen
2006-08-23 10:29 ` Stephane Eranian
2006-08-23 15:25 ` Christoph Hellwig
2006-08-23 15:53 ` Stephane Eranian
2006-08-23 20:57 ` Christoph Hellwig
2006-08-23 10:39 ` Stephane Eranian
2006-08-23 11:22 ` Andi Kleen
2006-08-23 12:14 ` Stephane Eranian
2006-08-23 12:29 ` Andi Kleen
2006-08-23 12:58 ` Stephane Eranian
2006-08-23 13:44 ` Andi Kleen [this message]
2006-08-23 13:48 ` Stephane Eranian
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=200608231544.26756.ak@suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=eranian@hpl.hp.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.