From: David Ahern <dsahern@gmail.com>
To: Yuanfang Chen <cyfmxc@gmail.com>
Cc: linux-kernel@vger.kernel.org, Namhyung Kim <namhyung@gmail.com>
Subject: Re: perf record: can I specify multiple events and use different sample-after value
Date: Sun, 26 Feb 2012 20:23:19 -0700 [thread overview]
Message-ID: <4F4AF727.2040105@gmail.com> (raw)
In-Reply-To: <CAJh9x3rxK42wFXqCASex1YwMKofWdZ=g-OnH43BHDtUjeMabbA@mail.gmail.com>
On 2/24/12 3:41 PM, Yuanfang Chen wrote:
> I think I'll settle with perf record for now. Still, unlike trace
> event, sample count is not meaningful for PMU event. Output of "perf
> script" does not include period value. One line of code will do the
> work.
>
> lude 17342 750118.202915: raw 0x3c: 86754 ffffffff8115f6b9
> __mem_cgroup_commit_char
> lude 17342 750118.203025: raw 0x3c: 1027634 ffffffff811344b9
> __mem_cgroup_commit_char
>
> 86754, 1027634 is the period value. But I'm not sure which is the PMU
> value, is it just period value, or period x sample after. If so, what
> is the sample after value?
You lost me. You modified perf-script to print the period?
Are you asking for the PMU counter value for 0x3c?
What perf commands are you running?
David
next prev parent reply other threads:[~2012-02-27 3:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 1:59 perf record: can I specify multiple events and use different sample-after value Yuanfang Chen
2012-02-22 6:01 ` Namhyung Kim
2012-02-22 11:40 ` Namhyung Kim
2012-02-22 19:03 ` Yuanfang Chen
2012-02-23 7:24 ` Namhyung Kim
[not found] ` <CAJh9x3o7HLGBWrwBaGgxXS-C9noQbKwh5BP_PAHomOOS6x9SYw@mail.gmail.com>
2012-02-23 18:52 ` Yuanfang Chen
2012-02-23 19:08 ` David Ahern
2012-02-24 22:41 ` Yuanfang Chen
2012-02-27 3:23 ` David Ahern [this message]
[not found] ` <CAJh9x3oO+-8Bc4UONG6RTmSeVFcuNHTKH5m2KsizaubmSojYmw@mail.gmail.com>
2012-02-27 13:58 ` Yuanfang Chen
2012-02-27 14:42 ` David Ahern
[not found] ` <CAJh9x3o3M+PWW8k6Ns51pQaMjEtWDmD3s8P0P_6_jro5zh66bA@mail.gmail.com>
2012-02-27 15:05 ` Fwd: " Yuanfang Chen
2012-02-22 18:57 ` Yuanfang Chen
2012-02-23 7:40 ` Namhyung Kim
2012-02-23 18:57 ` Yuanfang Chen
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=4F4AF727.2040105@gmail.com \
--to=dsahern@gmail.com \
--cc=cyfmxc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.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