public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephane Eranian <eranian@hpl.hp.com>
To: perfmon@napali.hpl.hp.com
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	oprofile-list@lists.sourceforge.net,
	perfctr-devel@lists.sourceforge.net
Subject: 2.6.17-rc1 perfmon2 new code base + libpfm available
Date: Wed, 5 Apr 2006 08:43:19 -0700	[thread overview]
Message-ID: <20060405154319.GD6232@frankl.hpl.hp.com> (raw)

Hello,

I have released another version of the perfmon new code base package.
This release is relative to 2.6.17-rc1

There were, once again, new system calls added. As such a new libpfm is
necessary.

This new kernel patch includes several changes:

	- Merged i386 and x86_64 perfmon.c architecture specific codes

	- Merged PMU description modules for em64t and p4.

	- support for automatic loading of PMU description modules if
	  CONFIG_KMOD=y. Make sure you run make modules_install

	- MIPS patches are back and are applied onto the mainline kernel

This release uses the new/mod patch breakdown for all architectures.
To apply, you can simply do:
	cat ../perfmon-new-base-060405/*.diff | patch -p1 

The new version of the library, libpfm, includes the following changes:

	- updated to match 2.6.17-rc1 new system call numbers

	- modified pfmlib.h to use 64-bit integer for generic PMC register
	  (submitted by Kevin Corry from IBM)

I have finally created a minimal home page for the project. So now
you can access the latest news and files from:

	http://perfmon2.sf.net

I received notification from SF.net, that the libpfm package has been installed
into our CVS repository. It should become visible fairly quickly now. Once this
happens, I will update the tree to include this new version of the library.

Enjoy,

-- 
-Stephane

             reply	other threads:[~2006-04-05 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-05 15:43 Stephane Eranian [this message]
2006-04-05 18:39 ` 2.6.17-rc1 perfmon2 new code base + libpfm available 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=20060405154319.GD6232@frankl.hpl.hp.com \
    --to=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