public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: acme@redhat.com, jolsa@redhat.com, eranian@google.com,
	linux-kernel@vger.kernel.org
Subject: perf user tool precise attribute broken in 3.5rc1+
Date: Thu, 7 Jun 2012 22:23:55 +0200	[thread overview]
Message-ID: <20120607202355.GQ27374@one.firstfloor.org> (raw)


With a perf user tool compiled from a 3.5rc1+ kernel I cannot
use the 'p' attribute anymore. Always get

ak@petrock:~> ./perf record -e cycles:p ./t

  Error: sys_perf_event_open() syscall returned with 22 (Invalid argument).  /bin/dmesg may provide additional information.

  Fatal: No CONFIG_PERF_EVENTS=y kernel support configured?

./t: Terminated

With an older perf it works, so the kernel is ok.

ak@petrock:~> ./perf record -e cycles:p ./t
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.005 MB perf.data (~217 samples) ]
ak@petrock:~> 


-Andi
-- 
ak@linux.intel.com -- Speaking for myself only.

             reply	other threads:[~2012-06-07 20:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07 20:23 Andi Kleen [this message]
2012-06-07 20:25 ` perf user tool precise attribute broken in 3.5rc1+ Stephane Eranian
2012-06-07 20:45   ` Andi Kleen
2012-06-07 20:49   ` Jiri Olsa
2012-06-07 20:57     ` Andi Kleen
2012-06-07 21:18       ` Jiri Olsa
2012-06-07 20:53 ` Stephane Eranian
2012-06-07 20:58   ` Andi Kleen
2012-06-07 21:28     ` Arnaldo Carvalho de Melo
2012-06-08  3:10       ` Andi Kleen
2012-06-08 15:48         ` Arnaldo Carvalho de Melo
2012-06-08 16:53           ` Andi Kleen
2012-06-08 21:55             ` Andi Kleen
2012-06-09 16:47               ` Arnaldo Carvalho de Melo
2012-12-04 12:02               ` Hassan Salehe Matar
2012-06-07 21:37     ` Stephane Eranian

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=20120607202355.GQ27374@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=acme@redhat.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@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