All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milian Wolff <mail@milianw.de>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf mem: invalid or unsupported event: 'cpu/mem-loads/pp'
Date: Sun, 14 Jun 2015 14:06:27 +0200	[thread overview]
Message-ID: <4386856.SFWvs8H8rN@agathebauer> (raw)
In-Reply-To: <1374544009.5545.2.camel@concordia>

[-- Attachment #1: Type: text/plain, Size: 927 bytes --]

On Tuesday 23 July 2013 11:46:49 Michael Ellerman wrote:
> On Mon, 2013-07-22 at 19:34 +0200, Milian Wolff wrote:
> > Hey there,
> > 
> > I just found perf mem in the output of perf help and wanted to try it:
> > 
> > $ perf mem record ls
> > invalid or unsupported event: 'cpu/mem-loads/pp'
> > Run 'perf list' for a list of valid events
> > 
> >  usage: perf record [<options>] [<command>]
> >  ...
> > 
> > Am I missing a kernel configuration? Or what is going on here?
> 
> You need a kernel that has mem-loads in
> /sys/bus/event_source/devices/cpu/events
> 
> Assuming you're on x86 you'll need a 3.10 or later kernel.

Sorry for the long delay. I wanted to try it out again today, but I still get 
the same error message above. This is with a 4.0.5 kernel and perf 4.0.3.

What is required to get mem-loads in the path specified above?

Bye
-- 
Milian Wolff
mail@milianw.de
http://milianw.de

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      reply	other threads:[~2015-06-14 12:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 17:34 perf mem: invalid or unsupported event: 'cpu/mem-loads/pp' Milian Wolff
2013-07-23  1:46 ` Michael Ellerman
2015-06-14 12:06   ` Milian Wolff [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=4386856.SFWvs8H8rN@agathebauer \
    --to=mail@milianw.de \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    /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.