From: Peter Zijlstra <peterz@infradead.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [RFC 1/4] lockdep: additional lock specific information when dumping locks
Date: Mon, 12 Jan 2015 16:06:33 +0100 [thread overview]
Message-ID: <20150112150633.GD25256@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1421074631-18831-1-git-send-email-sasha.levin@oracle.com>
On Mon, Jan 12, 2015 at 09:57:08AM -0500, Sasha Levin wrote:
> When dumping held locks, it might be useful to get additional lock-specific
> information about each lock.
>
> This is mainly useful to figure out who really holds each lock rather then
> who's just waiting on it, but it could be extended further or extended to
> the other lockdep users if required.
I really don't see the point in this; I would much rather have something
useful like:
http://lwn.net/Articles/579849/
next prev parent reply other threads:[~2015-01-12 15:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 14:57 [RFC 1/4] lockdep: additional lock specific information when dumping locks Sasha Levin
2015-01-12 14:57 ` [RFC 2/4] locking/mutex: additional lock " Sasha Levin
2015-01-12 14:57 ` [RFC 3/4] locking/rwsem: " Sasha Levin
2015-01-12 14:57 ` [RFC 4/4] locking/spinlock: " Sasha Levin
2015-01-12 15:06 ` Peter Zijlstra [this message]
2015-01-12 15:12 ` [RFC 1/4] lockdep: additional lock specific " Sasha Levin
2015-01-12 15:37 ` Peter Zijlstra
2015-01-12 16:06 ` Sasha Levin
2015-01-12 16:23 ` Peter Zijlstra
2015-01-13 5:18 ` Sasha Levin
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=20150112150633.GD25256@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sasha.levin@oracle.com \
/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