public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: eranian@hpl.hp.com
Cc: perfmon@napali.hpl.hp.com, linux-ia64@vger.kernel.org,
	oprofile-list@lists.sourceforge.net,
	perfctr-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [perfmon] 2.6.19 new perfmon code base + libpfm + pfmon
Date: Tue, 05 Dec 2006 12:24:36 -0500	[thread overview]
Message-ID: <4575AB54.2050509@redhat.com> (raw)
In-Reply-To: <20061204164644.GO31914@frankl.hpl.hp.com>

Stephane Eranian wrote:
> Hello,
> 
> I have released another version of the perfmon new code base packages.
> 
> There is no major updates in this version compared to 061127. This is 
> a convenience release so that people can use plain 2.6.19.
> 
> The perfmon2 kernel changes are:
> 	- fix UP exit bug in system-wide mode where the active context
> 	  accounting was done incorrectly.
> 	- MIPS update to correct register hardware addresses (Phil Mucci)
> 
> I have also released a new libpfm, libpfm-3.2-061204 with the
> following changes:
> 	- updated MIPS processor detection code
> 
> Also a new version of pfmon, pfmon-3.2-061204 with the following changes:
> 	- fix various perfmon v2.0 compatibility bugs for IA-64
> 	- fortify return values for read() (will Cohen)
> 	
> Both libpfm and pfmon releases work with kernel-patch 061127 or 061204.
> 
> You can grab the new packages at our web site:
> 
> 	 http://perfmon2.sf.net
> 
> Enjoy,
> 

Some of the ptrace functions (e.g. ptrace_may_attach in perfmon_syscall.c) 
being used in the perfmon kernel patches will go away with the utrace patches: 
http://people.redhat.com/roland/utrace/


-Will

  reply	other threads:[~2006-12-05 17:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-04 16:46 2.6.19 new perfmon code base + libpfm + pfmon Stephane Eranian
2006-12-05 17:24 ` William Cohen [this message]
2006-12-05 22:28   ` [perfmon] " Christoph Hellwig
2006-12-06 21:39     ` William Cohen

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=4575AB54.2050509@redhat.com \
    --to=wcohen@redhat.com \
    --cc=eranian@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oprofile-list@lists.sourceforge.net \
    --cc=perfctr-devel@lists.sourceforge.net \
    --cc=perfmon@napali.hpl.hp.com \
    /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