From: Manuel Selva <selva.manuel@gmail.com>
To: Martin Ichilevici de Oliveira <martin.i.oliveira@gmail.com>,
linux-perf-users@vger.kernel.org
Subject: Re: Event not supported
Date: Tue, 18 Feb 2014 19:22:07 +0100 [thread overview]
Message-ID: <5303A4CF.3060200@gmail.com> (raw)
In-Reply-To: <CAOanW0NszteQapi6MzaUhkPpYA6yAe+bTc8Vkz033MDA3ynd_w@mail.gmail.com>
Hi,
What is your CPU ?
Regarding the perf version, on my Ubuntu 13.04 running linux 3.11.0-15 I
successfully installed the associated perf version using:
sudo apt-get install linux-tools-3.11.0-15-generic
Manu
On 02/18/2014 05:51 PM, Martin Ichilevici de Oliveira wrote:
> Hello,
>
> I'm still learning perf, so I apologize in advance if my questions are
> too simple and not suited here. I did, however, searched the web and
> tried to find a solution by myself before posting to this mailing
> list.
>
> From my manufacturer's manual, I chose an event I'm interested in
> monitoring. They also list unit masks, as below:
>
> UnitMask Description
> 7 From Local node to Node 7
> 6 From Local node to Node 6
> 5 From Local node to Node 5
> 4 From Local node to Node 4
> 3 From Local node to Node 3
> 2 From Local node to Node 2
> 1 From Local node to Node 1
> 0 From Local node to Node 0
>
> The event is "CPU to DRAM Requests to Target Node" (NUMA machine) and
> it's number is 0x1E0. As I understood, I should precede the event with
> the unit mask. So, for example, if I'm interested in unit mask 2, I
> should type:
>
> perf stat -e r21e0 /bin/ls
>
> However, this results in a <not supported> message. This happened for
> all events that have a unit mask that I tried. Other events worked
> fine.
>
> I'm not sure whether I'm giving the right command or this is a problem
> with perf/kernel version. As it turned out, I'm running Ubuntu with
> kernel 3.11.10-03111002, but the latest available perf version from
> the repositories is 3.8.0-35, which is the one I'm using.
>
> Any help is appreciated.
>
> Thank you,
> Martin
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-02-18 18:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 16:51 Event not supported Martin Ichilevici de Oliveira
2014-02-18 18:22 ` Manuel Selva [this message]
2014-02-18 18:42 ` Martin Ichilevici de Oliveira
2014-02-18 19:50 ` Manuel Selva
2014-02-19 11:38 ` Martin Ichilevici de Oliveira
2014-02-19 12:59 ` Vince Weaver
2014-02-26 20:44 ` Martin Ichilevici de Oliveira
2014-02-26 21:38 ` Vince Weaver
2014-02-28 9:35 ` Martin Ichilevici de Oliveira
2014-03-11 16:53 ` Martin Ichilevici de Oliveira
2014-03-13 20:06 ` Vince Weaver
2014-02-19 14:08 ` Baptiste Lepers
2014-02-20 8:09 ` Jiri Olsa
-- strict thread matches above, loose matches on Subject: below --
2001-03-30 16:41 event " Ben Woodard
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=5303A4CF.3060200@gmail.com \
--to=selva.manuel@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=martin.i.oliveira@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.