From: 陳韋任 <chenwj@iis.sinica.edu.tw>
To: David Ahern <daahern@cisco.com>
Cc: Arun Sharma <asharma@fb.com>, linux-perf-users@vger.kernel.org
Subject: Re: perf script and raw events?
Date: Wed, 23 Mar 2011 09:25:52 +0800 [thread overview]
Message-ID: <20110323012552.GA2080@cs.nctu.edu.tw> (raw)
In-Reply-To: <4D892E0E.3010505@cisco.com>
Hi,
> What is that raw event? Where do you find the encodings for raw events?
You can try libpfm4.
$ git clone git://perfmon2.git.sourceforge.net/gitroot/perfmon2/libpfm4
`showevtinfo` in libpfm4/examples/ lists all events supported by the
CPU, including raw events.
`evt2raw` in libpfm4/perf_examples converts event names into raw event
recognized by perf.
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Parallel Processing Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667
prev parent reply other threads:[~2011-03-23 1:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110322224116.GA3794@dev1756.snc6.facebook.com>
2011-03-22 23:17 ` perf script and raw events? David Ahern
2011-03-23 0:44 ` Lin Ming
2011-03-23 1:25 ` 陳韋任 [this message]
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=20110323012552.GA2080@cs.nctu.edu.tw \
--to=chenwj@iis.sinica.edu.tw \
--cc=asharma@fb.com \
--cc=daahern@cisco.com \
--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).