linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephane Eranian <eranian@hpl.hp.com>
To: perfctr-devel@lists.sourceforge.net
Cc: perfmon@napali.hpl.hp.com, linux-ia64@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: new 2.6.15-rc6 perfmon2 patch
Date: Wed, 21 Dec 2005 14:09:13 -0800	[thread overview]
Message-ID: <20051221220913.GC8275@frankl.hpl.hp.com> (raw)
In-Reply-To: <20051220180744.GC5516@frankl.hpl.hp.com>

Hi,

I have released YET another version of the perfmon2 new code base.
This one is STILL relative to 2.6.15-rc6 and is called 2.6.15-rc6-v2.
This one DOES fix the panic on pfm_fmt_put()!

This patch includes compared to initial 2.6.15-rc6:

    - quick overview of perfmon2 README

    - fix the kernel panic on pfm_fmt_put()

    - save/restore of PMU state when NMI watchdog is
      enabled.

    - reinforced  checks in register_smpl_fmt()

    - revised checks to detect if a format/PMU description is
      builtin or module

    - sampling formats can now export the notification
      message queue depth they require.

    - MIPS patch updated to latest fixes.

You MUST use libpfm-3.2-051215 with this kernel due to
interface change for pfm_create_context().
As usual, you can download the latest packages from the
SourceForge website at:

http://www.sf.net/projects/perfmon2

This will hopefully be the last release for this year.

Happy Holidays.

-- 
-Stephane

      reply	other threads:[~2005-12-21 22:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-15 10:46 2.6.15-rc5-git3 perfmon2 new code base + libpfm available Stephane Eranian
2005-12-15 21:22 ` [Perfctr-devel] " William Cohen
2005-12-15 21:59   ` Stephane Eranian
2005-12-15 22:23     ` William Cohen
2005-12-15 23:15       ` Stephane Eranian
2005-12-20 16:05         ` William Cohen
2005-12-20 16:54           ` Matthew Wilcox
2005-12-20 18:07 ` 2.6.15-rc6 updated perfmon2 patch Stephane Eranian
2005-12-21 22:09   ` Stephane Eranian [this message]

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=20051221220913.GC8275@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 \
    --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;
as well as URLs for NNTP newsgroup(s).