From: David Ahern <dsahern@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: perf lock record fails
Date: Sun, 08 Jul 2012 19:53:58 -0600 [thread overview]
Message-ID: <4FFA39B6.4010903@gmail.com> (raw)
In-Reply-To: <874npkidlb.fsf@sejong.aot.lge.com>
On 7/6/12 7:06 PM, Namhyung Kim wrote:
> Hi, David
>
> On Fri, 06 Jul 2012 11:27:39 -0600, David Ahern wrote:
>> What config options need to be enabled for 'perf lock record' to work?
>> I tried a number of custom builds and stock Fedora kernels. I always
>> get:
>>
>> $ perf lock record -- sleep 1
>> invalid or unsupported event: 'lock:lock_acquire'
>>
>> Though trace_lock_acquire exists, CONFIG_LOCKDEP is set, and ftrace is
>> enabled.
>>
>> What am I missing?
>>
>
> Weird. AFAICS lock_acquire and lock_release depend on CONFIG_LOCKDEP,
> and lock_acquired and lock_contented depend on CONFIG_LOCK_STAT (I guess
> it should be warned/commented somewhere?). Maybe CONFIG_EVENT_TRACING?
CONFIG_EVENT_TRACING is set.
I started a comparison with other tracepoints to see if I can decipher
why they show up but none of the trace functions for the lock system do
(e.g., lock_acquire), but haven't had much time to spend on it. I was
hoping Steve or Frederic could explain it quicker. ;-)
David
prev parent reply other threads:[~2012-07-09 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 17:27 perf lock record fails David Ahern
2012-07-07 1:06 ` Namhyung Kim
2012-07-09 1:53 ` David Ahern [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=4FFA39B6.4010903@gmail.com \
--to=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.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).