From: Jiri Olsa <jolsa@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: Andi Kleen <andi@firstfloor.org>,
acme@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: perf user tool precise attribute broken in 3.5rc1+
Date: Thu, 7 Jun 2012 22:49:15 +0200 [thread overview]
Message-ID: <20120607204915.GA1698@m.redhat.com> (raw)
In-Reply-To: <CABPqkBSoCO4nSm==THVzVVu_cn=B5s4TZ_YpPxV73EGMNMgbrg@mail.gmail.com>
On Thu, Jun 07, 2012 at 10:25:47PM +0200, Stephane Eranian wrote:
> What CPU model?
+1, latest tip works for me ;)
jirka
>
> On Thu, Jun 7, 2012 at 10:23 PM, Andi Kleen <andi@firstfloor.org> wrote:
> >
> > 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.
next prev parent reply other threads:[~2012-06-07 20:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 20:23 perf user tool precise attribute broken in 3.5rc1+ Andi Kleen
2012-06-07 20:25 ` Stephane Eranian
2012-06-07 20:45 ` Andi Kleen
2012-06-07 20:49 ` Jiri Olsa [this message]
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=20120607204915.GA1698@m.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=eranian@google.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