On 02/03/2013 06:05 AM, Ingo Molnar wrote:
>
> * Sasha Levin wrote:
>
>> liblockdep is simply userspace lockdep. We can use that to analyze and
>> verify the locking in perf.
>>
>> Usage is simple, to compile perf with liblockdep all that's needed it:
>>
>> make LIBLOCK=[path to liblockdep]
* Sasha Levin wrote:
> liblockdep is simply userspace lockdep. We can use that to analyze and
> verify the locking in perf.
>
> Usage is simple, to compile perf with liblockdep all that's needed it:
>
> make LIBLOCK=[path to liblockdep]
Nice idea.
I'd suggest to link it in directly, li
liblockdep is simply userspace lockdep. We can use that to analyze and
verify the locking in perf.
Usage is simple, to compile perf with liblockdep all that's needed it:
make LIBLOCK=[path to liblockdep]
Once liblockdep support is compiled in, perf will yell if locking goes
wrong for any
liblockdep is simply userspace lockdep. We can use that to analyze and
verify the locking in perf.
Usage is simple, to compile perf with liblockdep all that's needed it:
make LIBLOCK=[path to liblockdep]
Once liblockdep support is compiled in, perf will yell if locking goes
wrong for any
4 matches
Mail list logo
