From: David Brownell <david-b@pacbell.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [patch 2.6.25-rc3] lockdep: add spin_lock_irq_nested()
Date: Tue, 26 Feb 2008 02:36:16 -0800 [thread overview]
Message-ID: <200802260236.17188.david-b@pacbell.net> (raw)
In-Reply-To: <1204019626.6242.225.camel@lappy>
On Tuesday 26 February 2008, Peter Zijlstra wrote:
>
> On Mon, 2008-02-25 at 14:33 -0800, David Brownell wrote:
>
> > > +#ifdef CONFIG_LOCKDEP
> > > +
> > > +/* tell lockdep that this IRQ's locks and its parent's locks are in
> > > + * different categories, so that it won't detect false recursion.
> > > + */
> > > +static struct lock_class_key gpio_lock_class;
> > > +
> > > +static inline void mark_gpio_locking(unsigned gpio_irq)
> > > +{
> > > + lockdep_set_class(&irq_desc[gpio_irq].lock, &gpio_lock_class);
> > > +}
> > > +
> > > +#else
> > > +
> > > + ...
>
> Glad to hear this works out for you.
Yeah, glad to have a localized fix rather than mucking with genirq.
> Just one note, you don't need the #ifdef mess here. struct
> lock_class_key is 0 bytes on !LOCKDEP and lockdep_set_class*() is
> defined away as well.
Hmm, then kernel/irq/handle.c shouldn't need #ifdefs either ... ;)
next prev parent reply other threads:[~2008-02-26 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 22:33 [patch 2.6.25-rc3] lockdep: add spin_lock_irq_nested() David Brownell
2008-02-26 9:53 ` Peter Zijlstra
2008-02-26 10:36 ` David Brownell [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-18 22:29 [patch/rfc 2.6.24-rc8-git] genirq: partial lockdep fixes David Brownell
2008-01-21 8:31 ` Peter Zijlstra
2008-01-21 18:22 ` David Brownell
2008-02-25 4:33 ` [patch 2.6.25-rc3] lockdep: add spin_lock_irq_nested() David Brownell
2008-02-25 10:20 ` Peter Zijlstra
2008-02-25 11:21 ` David Brownell
2008-02-25 13:17 ` Peter Zijlstra
2008-02-25 21:10 ` David Brownell
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=200802260236.17188.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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