From: eranian@googlemail.com
To: linux-kernel@vger.kernel.org
Subject: [patch 00/24] perfmon3: introduction
Date: Fri, 17 Oct 2008 08:05:07 -0700 (PDT) [thread overview]
Message-ID: <48f8a9a3.0437560a.656a.57c5@mx.google.com> (raw)
Hello,
This series of patches implements the perfmon interface which provides access
to the hardware performance counters of modern processors. In particular,
this version supports per-thread counting for all AMD64 processors, and
recent Intel processors with architectural PMU (Core Duo, Core 2, Atom).
It does not supersede Oprofile in this first implementation. Oprofile
and perfmon can be compiled in the same kernel, but only one can have
an active session at a time.
This implementation takes into account the various comments received from
previous reviews on LKML. This is a much simplified version compared to
the fully featured version maintained as a separate GIT tree on kernel.org.
This new version, named perfmon3, uses only 5 system calls (instead of 12).
Each call was carefully designed to allow for future extensions.
Full documentation is available in Documentation/perfmon.txt and is provided
by one of the patches.
Once this basic set of perfmon functionalities is upstream, we will build
on it and add other features such as support for sampling, event set
multiplexing and multi-architecture.
I will be releasing updated versions of libpfm and pfmon which can work
with this new API while continuing to work with the v2.x versions.
The patch series is against 2.6.27.
Please consider adding this patch series for 2.6.28.
Thanks to all the people who have contributed to this new release.
S.Eranian
--
next reply other threads:[~2008-10-17 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 15:05 eranian [this message]
2008-10-22 4:25 ` David Miller
2008-10-22 8:39 ` stephane eranian
2008-10-22 16:58 ` Jesse Barnes
2008-10-22 17:22 ` Andrew Morton
2008-10-23 7:19 ` stephane eranian
2008-11-10 2:41 ` Paul Mackerras
2008-11-10 15:24 ` stephane eranian
2008-11-11 0:29 ` 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=48f8a9a3.0437560a.656a.57c5@mx.google.com \
--to=eranian@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome