* perf lock record fails
@ 2012-07-06 17:27 David Ahern
2012-07-07 1:06 ` Namhyung Kim
0 siblings, 1 reply; 3+ messages in thread
From: David Ahern @ 2012-07-06 17:27 UTC (permalink / raw)
To: Frederic Weisbecker, Ingo Molnar, Steven Rostedt, LKML
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?
David
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: perf lock record fails
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
0 siblings, 1 reply; 3+ messages in thread
From: Namhyung Kim @ 2012-07-07 1:06 UTC (permalink / raw)
To: David Ahern; +Cc: Frederic Weisbecker, Ingo Molnar, Steven Rostedt, LKML
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?
Thanks,
Namhyung
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: perf lock record fails
2012-07-07 1:06 ` Namhyung Kim
@ 2012-07-09 1:53 ` David Ahern
0 siblings, 0 replies; 3+ messages in thread
From: David Ahern @ 2012-07-09 1:53 UTC (permalink / raw)
To: Namhyung Kim; +Cc: Frederic Weisbecker, Ingo Molnar, Steven Rostedt, LKML
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-07-09 1:54 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).