From: Peter Zijlstra <peterz@infradead.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
simon.wunderlich@s2003.tu-chemnitz.de,
Marek Lindner <lindner_marek@yahoo.de>
Subject: Re: Using nested locking for spin_lock_bh
Date: Sun, 15 Apr 2012 13:18:07 +0200 [thread overview]
Message-ID: <1334488687.28150.3.camel@twins> (raw)
In-Reply-To: <2108147.Aqyix6xDmB@bentobox>
On Wed, 2012-03-28 at 18:36 +0200, Sven Eckelmann wrote:
>
> Is there another way how this should be done or is there a general problem why
> there is no nested support for this incarnation of spin_lock?
No reason other than that it wasn't needed before now, but I see you've
resolved things with a lockdep_set_class() which works too.
prev parent reply other threads:[~2012-04-15 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 16:36 Using nested locking for spin_lock_bh Sven Eckelmann
2012-03-29 3:11 ` Yong Zhang
2012-03-29 10:41 ` Sven Eckelmann
2012-04-15 11:18 ` Peter Zijlstra [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=1334488687.28150.3.camel@twins \
--to=peterz@infradead.org \
--cc=lindner_marek@yahoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=sven@narfation.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