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: 2.6.15-rc6 updated perfmon2 patch
Date: Tue, 20 Dec 2005 18:07:44 +0000 [thread overview]
Message-ID: <20051220180744.GC5516@frankl.hpl.hp.com> (raw)
In-Reply-To: <20051215104604.GA16937@frankl.hpl.hp.com>
Hi,
I have released another verison of the perfmon2 new code base.
This one is relative to 2.6.15-rc6 and hopefully should
fix some of the problems people have reported.
This new kernel patch fixes the following:
- kernel panic in perfmon_pmu.c or perfmon_fmt.c
if PMU description or buffer format is compiled in.
- missing __user in perfmon_syscalls.c
- better handling of NMI reservation for X86-64, EM64T
and i386.
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
--
-Stephane
WARNING: multiple messages have this Message-ID (diff)
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: 2.6.15-rc6 updated perfmon2 patch
Date: Tue, 20 Dec 2005 10:07:44 -0800 [thread overview]
Message-ID: <20051220180744.GC5516@frankl.hpl.hp.com> (raw)
In-Reply-To: <20051215104604.GA16937@frankl.hpl.hp.com>
Hi,
I have released another verison of the perfmon2 new code base.
This one is relative to 2.6.15-rc6 and hopefully should
fix some of the problems people have reported.
This new kernel patch fixes the following:
- kernel panic in perfmon_pmu.c or perfmon_fmt.c
if PMU description or buffer format is compiled in.
- missing __user in perfmon_syscalls.c
- better handling of NMI reservation for X86-64, EM64T
and i386.
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
--
-Stephane
next prev parent reply other threads:[~2005-12-20 18:07 UTC|newest]
Thread overview: 18+ 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 10:46 ` Stephane Eranian
2005-12-15 21:22 ` [Perfctr-devel] 2.6.15-rc5-git3 perfmon2 new code base + libpfm William Cohen
2005-12-15 21:22 ` [Perfctr-devel] 2.6.15-rc5-git3 perfmon2 new code base + libpfm available William Cohen
2005-12-15 21:59 ` Stephane Eranian
2005-12-15 21:59 ` Stephane Eranian
2005-12-15 22:23 ` [Perfctr-devel] 2.6.15-rc5-git3 perfmon2 new code base + libpfm William Cohen
2005-12-15 22:23 ` [Perfctr-devel] 2.6.15-rc5-git3 perfmon2 new code base + libpfm available William Cohen
2005-12-15 23:15 ` Stephane Eranian
2005-12-15 23:15 ` Stephane Eranian
2005-12-20 16:05 ` [Perfctr-devel] 2.6.15-rc5-git3 perfmon2 new code base + libpfm William Cohen
2005-12-20 16:05 ` [Perfctr-devel] 2.6.15-rc5-git3 perfmon2 new code base + libpfm available William Cohen
2005-12-20 16:54 ` Matthew Wilcox
2005-12-20 16:54 ` Matthew Wilcox
2005-12-20 18:07 ` Stephane Eranian [this message]
2005-12-20 18:07 ` 2.6.15-rc6 updated perfmon2 patch Stephane Eranian
2005-12-21 22:09 ` new 2.6.15-rc6 " Stephane Eranian
2005-12-21 22:09 ` 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=20051220180744.GC5516@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.