linux-kernel - Re: [PATCH v2 7/7] perf: integrate liblockdep support into perf

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <510ED91F.6050601@oracle.com>
Date:	Sun, 03 Feb 2013 16:39:43 -0500
From:	Sasha Levin <sasha.levin@...cle.com>
To:	Ingo Molnar <mingo@...nel.org>
CC:	mingo@...hat.com, peterz@...radead.org, paulus@...ba.org,
	acme@...stprotocols.net, penberg@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 7/7] perf: integrate liblockdep support into perf

On 02/03/2013 06:05 AM, Ingo Molnar wrote:
> 
> * Sasha Levin <sasha.levin@...cle.com> 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, like we link in 
> libtraceevents.
> 
> Then it could be built via something like:
> 
>    make LOCKDEP=1
> 
> or so.
> 

Sounds good, I'll resend the series.


Thanks,
Sasha

--
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/