[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 07 Jul 2012 10:06:56 +0900
From: Namhyung Kim <namhyung@...nel.org>
To: David Ahern <dsahern@...il.com>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: perf lock record fails
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists