From: Dhaval Giani <dhaval.giani@oracle.com>
To: Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] lockdep: Show up to three levels for a deadlock scenario
Date: Tue, 19 Dec 2017 11:30:29 -0500 [thread overview]
Message-ID: <3317dd1a-1a39-3295-eb90-538be296dff8@oracle.com> (raw)
In-Reply-To: <20171214175931.mlvr7lk7bcnsqu5i@hirez.programming.kicks-ass.net>
On 2017-12-14 12:59 PM, Peter Zijlstra wrote:
> On Thu, Dec 14, 2017 at 12:38:52PM -0500, Steven Rostedt wrote:
>>
>> Currently, when lockdep detects a possible deadlock scenario that involves 3
>> or more levels, it just shows the chain, and a CPU sequence order of the
>> first and last part of the scenario, leaving out the middle level and this
>> can take a bit of effort to understand. By adding a third level, it becomes
>> easier to see where the deadlock is.
>
> So is anybody actually using this? This (together with the callchain for
> #0) is always the first thing of the lockdep output I throw away.
>
Yes :-). The other stuff is unreadable to people not you.
Dhaval
next prev parent reply other threads:[~2017-12-19 16:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 17:38 Steven Rostedt
2017-12-14 17:59 ` Peter Zijlstra
2017-12-14 18:19 ` Steven Rostedt
2017-12-19 16:30 ` Dhaval Giani [this message]
2017-12-19 16:46 ` Peter Zijlstra
2017-12-19 16:52 ` Steven Rostedt
2017-12-19 16:54 ` Dhaval Giani
2017-12-19 17:10 ` Steven Rostedt
2017-12-19 17:07 ` Peter Zijlstra
2017-12-19 17:11 ` Steven Rostedt
2017-12-19 17:29 ` 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=3317dd1a-1a39-3295-eb90-538be296dff8@oracle.com \
--to=dhaval.giani@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®