From: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Magnus Damm <magnus.damm@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"gregkh@suse.de" <gregkh@suse.de>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"hjk@linutronix.de" <hjk@linutronix.de>,
"lethal@linux-sh.org" <lethal@linux-sh.org>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: [PATCH] uio: uio_pdrv_genirq V2
Date: Thu, 10 Jul 2008 12:47:49 +0200 [thread overview]
Message-ID: <20080710104749.GA313@digi.com> (raw)
In-Reply-To: <20080710110225.0dd636cf@the-village.bc.nu>
Hello Alan,
Alan Cox wrote:
> On Thu, 10 Jul 2008 12:30:36 +0200
> Uwe Kleine-König <Uwe.Kleine-Koenig@digi.com> wrote:
>
> > Alan Cox wrote:
> > >
> > > > > + else if (!irq_on && !priv->irq_disabled)
> > > > > + disable_irq(dev_info->irq);
> > > > I'm not sure if this is a problem on SMP. Should you use
> > > > disable_irq_nosync here, too? Probably it's OK.
> > >
> > > That one will also deadlock.
> > Can you explain why? I think irqcontrol is only called in task context.
> > I only see one possible deadlock and that's disable_irq being called
> > while the irq is IRQ_INPROGRESS on the same cpu. I'm always willing to
> > learn.
>
> CPU0 (UIO IRQ) CPU1 (irqcontrol)
> take IRQ
> take spin lock
> spin on spinlock
> disable_irq (blocks)
Ah, OK, that's because uio_pdrv_genirq_handler and
uio_pdrv_genirq_irqcontrol share the lock.
Is this something that lockdep can detect?
Best regards and thanks for clearifying
Uwe
--
Uwe Kleine-König, Software Engineer
Digi International GmbH Branch Breisach, Küferstrasse 8, 79206 Breisach, Germany
Tax: 315/5781/0242 / VAT: DE153662976 / Reg. Amtsgericht Dortmund HRB 13962
next prev parent reply other threads:[~2008-07-10 10:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 3:52 [PATCH] uio: uio_pdrv_genirq V2 Magnus Damm
2008-07-10 6:56 ` Uwe Kleine-König
2008-07-10 8:46 ` Alan Cox
2008-07-10 10:30 ` Uwe Kleine-König
2008-07-10 10:02 ` Alan Cox
2008-07-10 10:47 ` Uwe Kleine-König [this message]
2008-07-11 6:15 ` Magnus Damm
2008-07-10 10:58 ` Hans J. Koch
2008-07-10 11:06 ` Uwe Kleine-König
2008-07-10 13:49 ` Hans J. Koch
2008-07-11 8:45 ` Magnus Damm
2008-07-11 9:00 ` Uwe Kleine-König
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=20080710104749.GA313@digi.com \
--to=uwe.kleine-koenig@digi.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=hjk@linutronix.de \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--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