From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: David Collins <collinsd@codeaurora.org>,
Liam Girdwood <lrg@slimlogic.co.uk>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: Deadlock scenario in regulator core
Date: Wed, 23 Mar 2011 00:11:28 +0000 [thread overview]
Message-ID: <20110323001128.GC2529@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1300838856.14261.35.camel@gandalf.stny.rr.com>
On Tue, Mar 22, 2011 at 08:07:36PM -0400, Steven Rostedt wrote:
> Note, I do not know this code well enough to say. I'm assuming that an
> rdevA on a rdevB->supply_list never has rdevB on its own
> rdevA->supply_list.
Correct.
> If this is the case, and that you only ever have a lock nesting of one,
> then sure, use the SINGLE_DEPTH_NESTING.
It'd be good if someone could update the documentation in the mutex code
so the usage were clear here - I don't want to see the locking become
any more complicated, especially not for relatively infrequently used
things like supplies.
Though we may be able to deal with this by simplifying the
implementation of supplies anyway.
next prev parent reply other threads:[~2011-03-23 0:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 22:02 Deadlock scenario in regulator core David Collins
2011-03-22 22:31 ` Mark Brown
2011-03-22 23:30 ` David Collins
2011-03-22 23:45 ` Mark Brown
2011-03-22 22:37 ` Steven Rostedt
2011-03-22 23:08 ` David Collins
2011-03-22 23:19 ` Steven Rostedt
2011-03-22 23:41 ` David Collins
2011-03-23 0:07 ` Steven Rostedt
2011-03-23 0:11 ` Mark Brown [this message]
2011-03-25 10:55 ` Peter Zijlstra
2011-03-23 0:01 ` Mark Brown
2011-03-23 0:38 ` Steven Rostedt
2011-03-23 10:42 ` Mark Brown
2011-03-25 10:59 ` Peter Zijlstra
2011-03-22 22:43 ` Mark Brown
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=20110323001128.GC2529@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=collinsd@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).