From: Sasha Levin <sasha.levin@oracle.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: torvalds@linux-foundation.org, mingo@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/9] liblockdep: userspace lockdep
Date: Thu, 09 May 2013 08:42:40 -0400 [thread overview]
Message-ID: <518B99C0.9010304@oracle.com> (raw)
In-Reply-To: <20130509085429.GA3039@dyad.programming.kicks-ass.net>
On 05/09/2013 04:54 AM, Peter Zijlstra wrote:
> On Thu, May 09, 2013 at 12:19:07AM -0400, Sasha Levin wrote:
>> liblockdep is a tiny wrapper built around kernel/lockdep.c. The aim is to
>> provide the same functionality the kernel gets from lockdep to userspace.
>>
>> The bulk of the code here is the LD_PRELOAD support which provides users
>> an easy way to test their code without having to integrate liblockdep into
>> said code. Simply doing:
>>
>> lockdep my_app
>>
>> Would provide lockdep support to my_app.
>>
>> There is also a small test suite to test both mutexes and rwlocks, it's
>> based on the tests in lib/locking-selftest.c.
>>
>> This entire patch series was reviewed by lockdep maintainers and accepted to
>> the tip tree previously. It was pulled out so that the potential merge of
>> liblockdep won't delay the rest of the commits in the tip locking tree.
>>
>> For some more background about this entire thing, the folks at LWN did
>> an awesome overview: http://lwn.net/Articles/536363/
>>
>>
>> Changes from v1:
>> - Addressed Peter's comments.
>>
>
> root@twins:/usr/src/linux-2.6/tools/lib/lockdep# make
> CC FPIC common.o
> In file included from ./uinclude/linux/lockdep.h:13:0,
> from /usr/src/linux-2.6/tools/lib/lockdep/common.c:4:
> ./../../../include/linux/lockdep.h:21:27: fatal error: linux/linkage.h: No such file or directory
> compilation terminated.
> make: *** [common.o] Error 1
Oh, Ingo had a similar problem - you're using Quilt and that mishandles the
creation of empty files. You'll need to poke it stronger :)
I did notice a different issue due to a recent commit to kernel/lockdep.c, I'll
resend it again.
Thanks,
Sasha
prev parent reply other threads:[~2013-05-09 12:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 4:19 [PATCH v2 0/9] liblockdep: userspace lockdep Sasha Levin
2013-05-09 4:19 ` [PATCH v2 1/9] lockdep: Be nice about building from userspace Sasha Levin
2013-05-09 4:19 ` [PATCH v2 2/9] liblockdep: Wrap kernel/lockdep.c to allow usage " Sasha Levin
2013-05-09 4:19 ` [PATCH v2 3/9] liblockdep: Add public headers for pthread_mutex_t implementation Sasha Levin
2013-05-09 4:19 ` [PATCH v2 4/9] liblockdep: Add pthread_mutex_t test suite Sasha Levin
2013-05-09 4:19 ` [PATCH v2 5/9] liblockdep: Add public headers for pthread_rwlock_t implementation Sasha Levin
2013-05-09 4:19 ` [PATCH v2 6/9] liblockdep: Add pthread_rwlock_t test suite Sasha Levin
2013-05-09 4:19 ` [PATCH v2 7/9] liblockdep: Support using LD_PRELOAD Sasha Levin
2013-05-09 4:19 ` [PATCH v2 8/9] liblockdep: Add the 'lockdep' user-space utility Sasha Levin
2013-05-09 4:19 ` [PATCH v2 9/9] liblockdep: Add a MAINTAINERS entry Sasha Levin
2013-05-09 8:54 ` [PATCH v2 0/9] liblockdep: userspace lockdep Peter Zijlstra
2013-05-09 12:42 ` Sasha Levin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=518B99C0.9010304@oracle.com \
--to=sasha.levin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox