From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Arun Sharma <arun@sharma-home.net>
Cc: Can Hankendi <hankendi@gmail.com>, linux-perf-users@vger.kernel.org
Subject: Re: [perfmon2] updating perf tool
Date: Mon, 14 Feb 2011 17:44:28 -0200 [thread overview]
Message-ID: <20110214194428.GE21384@ghostprotocols.net> (raw)
In-Reply-To: <AANLkTinYM-Sg2uQFkXFy25mSZZZEtTSAUNrA==CxJP0=@mail.gmail.com>
Em Fri, Feb 11, 2011 at 12:31:11PM -0800, Arun Sharma escreveu:
> On Fri, Feb 11, 2011 at 12:21 PM, Can Hankendi <hankendi@gmail.com> wrote:
> > Thanks for the reply. I've tried perf record -C 0 -e cycles sleep 1 but i
> > received an error: Couldn't record kernel reference relocation symbol. Is it
> > possible to create per core report by using perf stat -C 0,1 so that I can
> > have individual stats for each core?
>
> # ./perf stat -e cycles -A -a -- sleep 1
>
> Performance counter stats for 'sleep 1':
>
> CPU0 2,145,862,116 cycles
> CPU1 2,146,131,064 cycles
> CPU2 2,146,021,047 cycles
> [...]
>
> and you can grep out only the CPUs you're looking for.
>
> If you're looking to do something more complicated that really
> requires hacking up a script, I wrapped the perf_event_open syscall in
> python via swig.
>
> sys.py --cpulist
>
> may be interesting.
>
> http://perfmon2.git.sourceforge.net/git/gitweb.cgi?p=perfmon2/libpfm4;a=blob;f=python/sys.py;h=e3a44f24174b979694e2588592f759010b77621e;hb=f70e032b5b69cf5aa6f7e0da746b1817c64341e9
Interesting, have you seen the python binding in tip/perf/core?
- Arnaldo
next prev parent reply other threads:[~2011-02-14 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTim5QGwisxLEHHHECrE1nLSYFxzXEMu7hvTRy09=@mail.gmail.com>
2011-02-11 19:44 ` [perfmon2] updating perf tool Arun Sharma
[not found] ` <AANLkTimqRjUTzv+AO7zHCfXvA1RZFDTjyb-r0s_MVNTW@mail.gmail.com>
2011-02-11 20:31 ` Arun Sharma
2011-02-14 19:44 ` Arnaldo Carvalho de Melo [this message]
2011-02-14 20:08 ` Arun Sharma
2011-02-14 20:48 ` Arnaldo Carvalho de Melo
2011-02-14 22:04 ` Arun Sharma
2011-02-15 1:24 ` Arnaldo Carvalho de Melo
2011-02-17 20:41 ` Arun Sharma
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=20110214194428.GE21384@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=arun@sharma-home.net \
--cc=hankendi@gmail.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).