mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephane Eranian <eranian@hpl.hp.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 18/18] 2.6.17.9 perfmon2 patch for review: new x86_64 files
Date: Wed, 23 Aug 2006 05:14:34 -0700	[thread overview]
Message-ID: <20060823121434.GE697@frankl.hpl.hp.com> (raw)
In-Reply-To: <200608231322.44106.ak@suse.de>

Andi,

On Wed, Aug 23, 2006 at 01:22:44PM +0200, Andi Kleen wrote:
> 
> > I have a second thought on this. AMD has architected the performance counters.
> 
> Quote:
> >>
> Implementations are not required to support the performance
> c o u n t e rs and the event-select registers, or the time-stamp
> counter. The presence of these features can be determined by
> <<
> 
At the end of this paragraph then mention using CPUID to determine
the presence of the counters. AFAIK, there is no feature bit
covering performance monitoring. Does that mean we are left
with having to check the family and model number just like on
Intel?


> Also all code I've seen checked the family at least.
> 
> 
> > Their specification is not part of a model specific documentation but
> > part of the AMD64 architecure. 
> 
> The high level specification is, but not the actual counters for once.
> 
> > What I don't not quite understand with the K7, K8 terminology is the
> > relation/dependencies with the AMD64 architecture specification.
> AMD64 gives a high level register format, K7/K8 is the actual list 
> of performance counters.

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
	2/ AMD64 Architecture Programmer's Manual is the generic AMD64 description

So in theory, we should have:
	- a generic PMU description for the architected PMU  as described in 2/
	- a K7/K8 PMU description table for Athlon64 and Opteron64 as described in 1/

AFAIK, K7/K8 do not add anything to the architected PMU. I'll rename what we have to perfmon_k8.c
to make it more explicit.

-- 
-Stephane

  reply	other threads:[~2006-08-23 12:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23  8:06 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 [this message]
2006-08-23 12:29         ` Andi Kleen
2006-08-23 12:58           ` Stephane Eranian
2006-08-23 13:44             ` Andi Kleen
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=20060823121434.GE697@frankl.hpl.hp.com \
    --to=eranian@hpl.hp.com \
    --cc=ak@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®