lkml.org 
[lkml]   [2010]   [Mar]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH RFC 00/11] lock monitor: Separate features related to lock

* Frederic Weisbecker <fweisbec@gmail.com> wrote:

> > You add chained indirect calls into all lock ops, that's got to hurt.
>
> Well, the idea was not bad at the first glance. It was separating lockdep
> and lock events codes.
>
> But indeed, the indirect calls plus the locking are not good for such a fast
> path.

What would be nice to have is some sort of dynamic patching approach to enable
_both_ lockdep, lockstat and perf lock.

If TRACE_EVENT() tracepoints were patchable we could use them. (but they arent
right now)

Ingo


\
 
 \ /
  Last update: 2010-03-17 10:55    [W:0.107 / U:0.072 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site