perf lock record fails
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
Hi, David
Quoted 4 lines · David Ahern
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:
Quoted 8 lines
$ perf lock record -- sleep 1 invalid or unsupported event: 'lock:lock_acquire'Though
trace_lock_acquireexists,CONFIG_LOCKDEPis 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
Quoted 13 lines · Namhyung Kim
Hi, David
Quoted 10 lines · David Ahern
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_acquireexists,CONFIG_LOCKDEPis set, and ftrace is enabled.
Quoted 6 lines
Quoted 2 lines
What am I missing?
Weird. AFAICS
lock_acquireandlock_releasedepend onCONFIG_LOCKDEP, andlock_acquiredandlock_contenteddepend onCONFIG_LOCK_STAT(I guess it should be warned/commented somewhere?). MaybeCONFIG_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