linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Omar Awile <omar.awile@cern.ch>
To: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Cc: Aram Santogidis <aram.santogidis@cern.ch>
Subject: perf record and intel_cqm/llc_occupancy
Date: Wed, 22 Jun 2016 15:42:25 +0000	[thread overview]
Message-ID: <etPan.576ab1e0.2383613b.84d3@cern.ch> (raw)

Dear perf users,

I have a question regarding perf’s support for Intel Cache Monitoring Technology. For the event intel_cqm/llc_occupancy, ‘perf stat’ works fine but ‘perf record’ does not. For example when I execute:

> perf record -e intel_cqm/llc_occupancy/ sleep 1

I get  

Error:
The sys_perf_event_open() syscall returned with 22 (Invalid argument) for event (intel_cqm/llc_occupancy/).
/bin/dmesg may provide additional information.
No CONFIG_PERF_EVENTS=y kernel support configured?

but when I execute:

> perf stat -e intel_cqm/llc_occupancy/ sleep 1

I get

Performance counter stats for 'sleep 1':

   40,960.00 Bytes intel_cqm/llc_occupancy/
   
   1.001455067 seconds time elapsed


* My perf and kernel version is 4.6.2-1.el7.elrepo.x86_64.
* cat /proc/sys/kernel/perf_event_paranoid returns -1
* The CPU is the E5-2630 v4 2.20GHz “Broadwell”.

Is it possible that for intel_cqm/llc_occupancy interrupts are not supported? In that case it wouldn’t be more appropriate to return ENOTSUP instead of EINVAL?

Thanks a lot in advance,

Omar

--
Omar Awile, Ph.D.
Systems Performance Engineer
CERN - 513/R-046



             reply	other threads:[~2016-06-22 15:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 15:42 Omar Awile [this message]
2016-06-23 20:53 ` perf record and intel_cqm/llc_occupancy Andi Kleen
2016-06-24 12:27   ` Omar Awile
2016-06-24 16:43     ` Andi Kleen

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=etPan.576ab1e0.2383613b.84d3@cern.ch \
    --to=omar.awile@cern.ch \
    --cc=aram.santogidis@cern.ch \
    --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).