From: Peter Zijlstra <peterz@infradead.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Ingo Molnar <mingo@kernel.org>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [Patch v5 0/9] liblockdep: userspace lockdep
Date: Sat, 9 Nov 2013 17:01:20 +0100 [thread overview]
Message-ID: <20131109160120.GD4971@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <527D1992.9000209@oracle.com>
On Fri, Nov 08, 2013 at 12:04:18PM -0500, Sasha Levin wrote:
> >
> >* Sasha Levin <sasha.levin@oracle.com> wrote:
> >
> >>On 07/08/2013 04:39 AM, Ingo Molnar wrote:
> >>>
> >>>* Sasha Levin <sasha.levin@oracle.com> wrote:
> >>>
> >>>>>>The other issue is that with lock classes disabled you have to hit an
> >>>>>>actual deadlock to trigger any output.
> >>>>>>
> >>>>>>I.e. much of the power of lockdep is diminished :-/ When actual
> >>>>>>deadlocks are triggered then it's not particularly complex to debug
> >>>>>>user-space apps: gdb the hung task(s) and look at the backtraces.
> >>>>>
> >>>>>Lock classes are disabled only if you're using the LD_PRELOAD method
> >>>>>of testing. If you actually re-compile your code with the library (by
> >>>>>just including the header and setting a #define to enable it) you will
> >>>>>have lock classes.
> >>>>
> >>>>Hi Ingo,
> >>>>
> >>>>Just wondering if you're planning on pushing it over to Linus from your
> >>>>tree, or should I go ahead and do it on my own?
> >>>
> >>>PeterZ is in favor as well so I'll apply them after the merge window, for
> >>>v3.12.
> >>
> >>Hi Ingo,
> >>
> >>Do you intend to send liblockdep in this merge window as planned?
> >
> >If Peter agrees with them and picks them up then the next merge window
> >would be fine I guess.
>
> Ping? Anyone?
Urgh, I missed Ingo throwing the ball back in my court.. sorry about
that. I'll have a look on Monday.
next prev parent reply other threads:[~2013-11-09 16:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 22:41 Sasha Levin
2013-06-13 22:41 ` [Patch v5 1/9] lockdep: Be nice about building from userspace Sasha Levin
2013-06-13 22:41 ` [Patch v5 2/9] liblockdep: Wrap kernel/lockdep.c to allow usage " Sasha Levin
2013-11-27 14:08 ` [tip:core/locking] liblockdep: Wrap kernel/locking/ lockdep.c " tip-bot for Sasha Levin
2013-06-13 22:41 ` [Patch v5 3/9] liblockdep: Add public headers for pthread_mutex_t implementation Sasha Levin
2013-11-27 14:08 ` [tip:core/locking] " tip-bot for Sasha Levin
2013-06-13 22:41 ` [Patch v5 4/9] liblockdep: Add pthread_mutex_t test suite Sasha Levin
2013-11-27 14:08 ` [tip:core/locking] " tip-bot for Sasha Levin
2013-06-13 22:41 ` [Patch v5 5/9] liblockdep: Add public headers for pthread_rwlock_t implementation Sasha Levin
2013-11-27 14:09 ` [tip:core/locking] " tip-bot for Sasha Levin
2013-06-13 22:41 ` [Patch v5 6/9] liblockdep: Add pthread_rwlock_t test suite Sasha Levin
2013-11-27 14:09 ` [tip:core/locking] " tip-bot for Sasha Levin
2013-06-13 22:41 ` [Patch v5 7/9] liblockdep: Support using LD_PRELOAD Sasha Levin
2013-11-27 14:09 ` [tip:core/locking] " tip-bot for Sasha Levin
2013-06-13 22:41 ` [Patch v5 8/9] liblockdep: Add the 'lockdep' user-space utility Sasha Levin
2013-11-27 14:09 ` [tip:core/locking] " tip-bot for Sasha Levin
2013-06-13 22:41 ` [Patch v5 9/9] liblockdep: Add a MAINTAINERS entry Sasha Levin
2013-11-27 14:09 ` [tip:core/locking] " tip-bot for Sasha Levin
2013-06-26 12:24 ` [Patch v5 0/9] liblockdep: userspace lockdep Peter Zijlstra
2013-06-26 15:53 ` Ingo Molnar
2013-06-26 19:38 ` Sasha Levin
2013-06-27 9:05 ` Ingo Molnar
2013-06-27 9:07 ` Ingo Molnar
2013-06-27 13:55 ` Sasha Levin
2013-07-08 1:14 ` Sasha Levin
2013-07-08 8:39 ` Ingo Molnar
2013-09-12 17:40 ` Sasha Levin
2013-09-12 18:01 ` Ingo Molnar
2013-09-14 16:59 ` Sasha Levin
2013-11-08 17:04 ` Sasha Levin
2013-11-09 16:01 ` Peter Zijlstra [this message]
2013-11-11 15:56 ` Peter Zijlstra
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=20131109160120.GD4971@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sasha.levin@oracle.com \
--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
Powered by JetHome