public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: Stephane Eranian <eranian@frankl.hpl.hp.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Stephane Eranian <eranian@hpl.hp.com>
Subject: Re: [PATCH 11/16] 2.6.17-rc6 perfmon2 patch for review: new i386 files
Date: Sun, 18 Jun 2006 02:07:54 -0400	[thread overview]
Message-ID: <200606180210_MC3-1-C2BF-E5CE@compuserve.com> (raw)

In-Reply-To: <200606150907.k5F97e7A008202@frankl.hpl.hp.com>

On Thu, 15 Jun 2006 02:07:40 -0700, Stephane Eranian wrote:

> This patch contains the new i386 files
> 
> 
> 
> 
> --- linux-2.6.17-rc6.orig/arch/i386/perfmon/Kconfig   1969-12-31 16:00:00.000000000 -0800
> +++ linux-2.6.17-rc6/arch/i386/perfmon/Kconfig        2006-06-13 06:58:08.000000000 -0700
> @@ -0,0 +1,48 @@
> +menu "Hardware Performance Monitoring support"
> +config PERFMON
> +     bool "Perfmon2 performance monitoring interface"
> +     select X86_LOCAL_APIC
> +     default y
> +     help
> +       include the perfmon2 performance monitoring interface
> +       in the kernel. See <http://perfmon2.sf.net/> for
> +       more details. If you're unsure, say Y.
> +
> + config PERFMON_P6
> +     tristate "Support for P6/Pentium M processor hardware performance counters"
> +     depends on PERFMON
> +     default m
> +     help
> +     Enables support for the P6-style hardware performance counters.
> +     To be used for P6 processors (Pentium III, PentiumPro) and also
> +     for Pentium M.
> +     If unsure, say M.
> +
> +config PERFMON_P4
> +     tristate "Support for 32-bit P4/Xeon hardware performance counters"
> +     depends on PERFMON
> +     default m
> +     help
> +     Enables support for the 32-bit P4/Xeon style hardware performance
> +     counters.
> +     If unsure, say M.
> +
> +config PERFMON_GEN_IA32
> +     tristate "Support for the architected IA-32 PMU"
> +     depends on PERFMON
> +     default m
> +     help
> +     Enables support for the architected IA-32 hardware performance counters.
> +     You need a Core Duo/Solo processor or newer for this work.
> +     If unsure, say M.
> +
> +config PERFMON_P4_PEBS
> +     tristate "Support for Intel P4 PEBS sampling format"
> +     depends on PERFMON_P4
> +     default m
> +     help
> +     Enables support for Precise Event-Based Sampling (PEBS) on the Intel P4
> +     processors which support it.  Does not work with P6 processors.
> +     If unsure, say m.
> +
> +endmenu

What do I pick for i386 kernel on Athlon64 hardware?  P6?  There's no help for
that (or Athlon/Sempron processors.)
-- 
Chuck
 "You can't read a newspaper if you can't read."  --George W. Bush

             reply	other threads:[~2006-06-18  6:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-18  6:07 Chuck Ebbert [this message]
2006-06-18 12:24 ` [PATCH 11/16] 2.6.17-rc6 perfmon2 patch for review: new i386 files Kevin Corry
  -- strict thread matches above, loose matches on Subject: below --
2006-06-18 15:55 Chuck Ebbert
2006-06-15  9:07 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=200606180210_MC3-1-C2BF-E5CE@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=eranian@frankl.hpl.hp.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox