The Linux Kernel Mailing List
 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 03:39:56 -0700	[thread overview]
Message-ID: <20060823103956.GB697@frankl.hpl.hp.com> (raw)
In-Reply-To: <p73fyfn7nzz.fsf@verdi.suse.de>

Andi,

On Wed, Aug 23, 2006 at 12:19:44PM +0200, Andi Kleen wrote:
> > +config X86_64_PERFMON_AMD64
> > +	tristate "Support 64-bit mode AMD64 hardware performance counters"
> > +	depends on PERFMON
> > +	default m
> 
> No default m please.  If someone just presses return in make oldconfig
> with a new kernel they don't want all kinds of new random optional drivers.
> 
> I think I would prefer to call it _K8, because in theory new AMD CPUs
> might have difference performance counters.
> 
I have a second thought on this. AMD has architected the performance counters.
Their specification is not part of a model specific documentation but
part of the AMD64 architecure.  If they were to radically change the
way performance counters are defined, then the processor would violate the
architecture. They can certainely extened the architecture, e.g., have more
than 4 counters. Those new counters could be model-specific, in which case
I would create a model-specific PMU description for it. If they want
to extened the capability for all new processors, I think a cleaner
way would be to update the architecture and then we could update the
descsription we have.

What I don't not quite understand with the K7, K8 terminology is the
relation/dependencies with the AMD64 architecture specification.

--
-Stephane

  parent reply	other threads:[~2006-08-23 10:50 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 [this message]
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
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=20060823103956.GB697@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