public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephane Eranian <eranian@hpl.hp.com>
To: perfctr-devel@lists.sourceforge.net
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Perfctr-devel] 2.6.14-rc2-mm1 new perfmon2 kernel patch available
Date: Thu, 29 Sep 2005 01:57:27 +0000	[thread overview]
Message-ID: <20050929015727.GB5211@frankl.hpl.hp.com> (raw)
In-Reply-To: <20050928103331.GB3808@frankl.hpl.hp.com>

Hello,

An updated version of the kernel patch I released yesterday
is available. It fixes the following problems:
	- compilation errors on Fedora Core 4 with gcc-4.x (reported by John Reiser)
	- range restriction not working on Itanium processors.
	- time-based event set switching not working on X86-64

You can grab the new release at:
	http://www.sf.net/projects/perfmon2

as kernel-patch: 2.6.14-rc2-mm1-050929

On Wed, Sep 28, 2005 at 03:33:31AM -0700, Stephane Eranian wrote:
> Hello everyone,
> 
> I am pleased to announce that I have released an  updated version
> of new-perfmon2 code base. This patch is against 2.6.14-rc2-mm1.
> 
> This new releases includes:
> 	- several bug fixes
> 	- many performance improvements (a PMD read on Itanium2 is down to 645 cycles).
> 	- a lot of code simplifications
> 	- support for P4/Xeon 32-bit (e.g., family 15 model 2).
> 	  includes support for HyperThreading(HT).
> 	- a P4/Xeon 32-bit sampling format for Precise Event Based sampling (PEBS)
> 
> The patch is known to work for all Itanium processors, P6/Pentium M,
> AMD X86-64, P4/Xeon 32-bit. I do not have a lot of user level support for P4 so
> testing was limited. Hopefully some people on this list may help with this.
> The EM64T is currently broken and must be updated to match the level of
> the P4/Xeon 32-bit version. The ppc64 portion has not been tested at all,
> it might not even compile.
> 
> For all PMU models, the mapping from PMC/PMD to actual PMU registers is
> accessible through /proc/perfmon_map. That is useful for people porting
> applications from other interfaces.
> 
> I encourage everybody to test this patch on their machine and report any
> problems.
> 
> You can download the new patch from our project website at:
> 
> 	http://www.sf.net/projects/perfmon2
> 
> as release: 2.6.14-rc2-mm1-050928
> 
> Enjoy,
> 
> -- 
> -Stephane
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Perfctr-devel mailing list
> Perfctr-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/perfctr-devel

-- 

-Stephane

  reply	other threads:[~2005-09-29  1:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <44BDAFB888F59F408FAE3CC35AB4704102225AA9@orsmsx409>
     [not found] ` <20050928040218.GB3170@frankl.hpl.hp.com>
2005-09-28 10:33   ` 2.6.14-rc2-mm1 new perfmon2 kernel patch available Stephane Eranian
2005-09-29  1:57     ` Stephane Eranian [this message]
2005-09-29  2:07       ` new beta of libpfm-3.2 for IA-64/P6/X86-64 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=20050929015727.GB5211@frankl.hpl.hp.com \
    --to=eranian@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perfctr-devel@lists.sourceforge.net \
    /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