From: Chulmin Kim <cmkim@core.kaist.ac.kr>
To: linux-perf-users@vger.kernel.org
Subject: PEBS event monitoring
Date: Thu, 29 Nov 2012 15:08:16 +0900 [thread overview]
Message-ID: <50B6FBD0.1010406@core.kaist.ac.kr> (raw)
Hi, all.
Sorry for consecutive basic questions.
I am about to use PEBS monitoring of Intel CPU. (westmere)
Let me elaborate pfmon example a bit.
% pfmon --smpl-module=pebs -einstructions_retired --inv=1
--counter-mask=1 --long-smpl-periods=2660000 -uk -- foo
# counts %self %cum code addr
1976 70.67% 70.67% 0x00000000004005e9
710 25.39% 96.07% 0x00000000004005f1
61 2.18% 98.25% 0x00000000004005e0
21 0.75% 99.00% 0x00000000004005ed
10 0.36% 99.36% 0x00000000004005f4
2 0.07% 99.43% 0xffffffff80583110
2 0.07% 99.50% 0xffffffff8024b4f8
As shown in the above,
I want to get the count number attached with address information.
While the example is only for retired instruction event, I want the same
thing for memory event (mem_load_retired) using Perf.
Is there any guide for this issue?
next reply other threads:[~2012-11-29 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 6:08 Chulmin Kim [this message]
2012-11-29 7:06 ` PEBS event monitoring Namhyung Kim
2012-11-29 10:18 ` Chulmin Kim
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=50B6FBD0.1010406@core.kaist.ac.kr \
--to=cmkim@core.kaist.ac.kr \
--cc=linux-perf-users@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;
as well as URLs for NNTP newsgroup(s).