From: Ingo Molnar <mingo@elte.hu>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Eric Dumazet" <eric.dumazet@gmail.com>,
"Stephane Eranian" <eranian@google.com>
Subject: Re: perf, x86: Provide a PEBS capable cycle event
Date: Wed, 26 Jan 2011 12:37:40 +0100 [thread overview]
Message-ID: <20110126113740.GA13911@elte.hu> (raw)
In-Reply-To: <201101062000.p06K0ESw011195@hera.kernel.org>
* Linux Kernel Mailing List <linux-kernel@vger.kernel.org> wrote:
> Gitweb: http://git.kernel.org/linus/7639dae0ca11038286bbbcda05f2bef601c1eb8d
> Commit: 7639dae0ca11038286bbbcda05f2bef601c1eb8d
> Parent: abe43400579d5de0078c2d3a760e6598e183f871
> Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> AuthorDate: Tue Dec 14 21:26:40 2010 +0100
> Committer: Ingo Molnar <mingo@elte.hu>
> CommitDate: Thu Dec 16 11:36:44 2010 +0100
>
> perf, x86: Provide a PEBS capable cycle event
>
> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> LKML-Reference: <new-submission>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---
> arch/x86/kernel/cpu/perf_event_intel.c | 26 ++++++++++++++++++++++++++
> 1 files changed, 26 insertions(+), 0 deletions(-)
btw., precise profiling via PEBS:
perf record -e cycles:p ...
works pretty nicely now on Nehalem CPUs and later.
Could we perhaps make perf record and perf top default to cycles:p on x86, and
silently fall back to regular cycles events if the CPU does not support this event
type?
That would make our profiles more precise by default - without users having to do
anything funky.
Thanks,
Ingo
next parent reply other threads:[~2011-01-26 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201101062000.p06K0ESw011195@hera.kernel.org>
2011-01-26 11:37 ` Ingo Molnar [this message]
2011-01-26 12:00 ` perf, x86: Provide a PEBS capable cycle event Stephane Eranian
2011-01-26 12:06 ` Ingo Molnar
2011-01-26 13:29 ` Stephane Eranian
2011-01-26 13:58 ` Ingo Molnar
2011-02-01 14:36 ` 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=20110126113740.GA13911@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=eric.dumazet@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.