From: Ingo Molnar <mingo@elte.hu>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Nobin Mathew <nobin.mathew@gmail.com>,
Jiri Slaby <jirislaby@gmail.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Robert Hancock <hancockr@shaw.ca>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: sharing interrupt between PCI device
Date: Mon, 10 Nov 2008 08:58:27 +0100 [thread overview]
Message-ID: <20081110075827.GE2093@elte.hu> (raw)
In-Reply-To: <20081110075115.GA13239@colo.lackof.org>
* Grant Grundler <grundler@parisc-linux.org> wrote:
> [+ingo - question for you about disable_irq() below]
> The same problem exists with disable_irq() : only takes a global
> IRQ# and no additional identifying information to prevent disabling
> a shared IRQ. So I'm not sure if this is a bug with ACPI or design
> flaw in generic IRQ APIs. Ingo?
that's how disable_irq() always worked: it disables all handlers on
that IRQ#. If the IRQ# is shared, it disables all handlers.
Ingo
next prev parent reply other threads:[~2008-11-10 7:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.h7+lofM1lpbRM5V4/ti5d7RwXuM@ifi.uio.no>
2008-11-05 0:28 ` sharing interrupt between PCI device Robert Hancock
2008-11-05 7:49 ` Nobin Mathew
2008-11-05 8:36 ` Jiri Slaby
2008-11-05 9:20 ` Nobin Mathew
2008-11-06 6:11 ` Nobin Mathew
2008-11-06 7:44 ` Nobin Mathew
2008-11-06 21:24 ` Jiri Slaby
2008-11-07 5:46 ` Nobin Mathew
2008-11-08 7:57 ` Grant Grundler
2008-11-08 9:49 ` Jiri Slaby
2008-11-08 11:53 ` Nobin Mathew
2008-11-08 11:57 ` Jiri Slaby
2008-11-08 17:27 ` Grant Grundler
2008-11-08 19:10 ` Jiri Slaby
2008-11-08 19:15 ` Grant Grundler
2008-11-10 6:35 ` Nobin Mathew
2008-11-10 6:39 ` Nobin Mathew
2008-11-10 6:47 ` Nobin Mathew
2008-11-10 7:51 ` Grant Grundler
2008-11-10 7:58 ` Ingo Molnar [this message]
2008-11-10 10:31 ` Nobin Mathew
2008-11-10 15:42 ` Nobin Mathew
2008-11-10 20:34 ` Grant Grundler
2008-11-11 4:57 ` Nobin Mathew
2008-11-11 16:24 ` Altobelli, David
2008-11-11 18:49 ` Robert Hancock
2008-11-10 20:33 ` Grant Grundler
2008-11-03 13:32 Nobin Mathew
2008-11-03 14:44 ` Jiri Slaby
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=20081110075827.GE2093@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=grundler@parisc-linux.org \
--cc=hancockr@shaw.ca \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nobin.mathew@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.