From: Jiri Olsa <jolsa@redhat.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf and uncore events
Date: Wed, 24 Oct 2012 22:48:57 +0200 [thread overview]
Message-ID: <20121024204857.GA1018@krava.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1210241627360.1411@vincent-weaver-1.um.maine.edu>
On Wed, Oct 24, 2012 at 04:32:00PM -0400, Vince Weaver wrote:
>
> So has anyone actually ever used perf to measure uncore events?
>
> I have a 3.6 kernel on a Sandybridge machine and the uncore directories
> definitely show up in
> /sys/bus/event_source/devices/
>
> But if I try
> ./perf stat -a -e "uncore_imc_0/event=0xff,umask=0x00" /bin/ls
> I get:
> invalid or unsupported event: 'uncore_imc_0/event=0xff,umask=0x00'
> Run 'perf list' for a list of valid events
> [...]
by quick look, it seems you're missing closing '/'
./perf stat -a -e "uncore_imc_0/event=0xff,umask=0x00/" /bin/ls
jirka
next prev parent reply other threads:[~2012-10-24 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 20:32 perf and uncore events Vince Weaver
2012-10-24 20:48 ` Jiri Olsa [this message]
2012-10-24 21:21 ` Vince Weaver
2012-10-25 10:18 ` Jiri Olsa
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=20121024204857.GA1018@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=vincent.weaver@maine.edu \
/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).