From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Stephane Eranian <eranian@google.com>,
jolsa@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: perf user tool precise attribute broken in 3.5rc1+
Date: Thu, 7 Jun 2012 18:28:00 -0300 [thread overview]
Message-ID: <20120607212759.GD30641@infradead.org> (raw)
In-Reply-To: <20120607205836.GT27374@one.firstfloor.org>
Em Thu, Jun 07, 2012 at 10:58:36PM +0200, Andi Kleen escreveu:
> On Thu, Jun 07, 2012 at 10:53:19PM +0200, Stephane Eranian wrote:
> > 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?
> > >
> > Remember that PEBS is disabled on SNB unless you have the new ucode + my patch.
>
> This is not the problem. This was actually a -E where it was not disabled
> in my tree. And the older perf binary works, so it's clearly not a kernel
> problem.
Are you sure the old one works? Perhaps it silently falls back to
cpu-clock?
What 'perf evlist -v' says?
- Arnaldo
next prev parent reply other threads:[~2012-06-07 21:28 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
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 [this message]
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=20120607212759.GD30641@infradead.org \
--to=acme@redhat.com \
--cc=andi@firstfloor.org \
--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 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.