Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754187AbYKJH7E (ORCPT ); Mon, 10 Nov 2008 02:59:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753366AbYKJH6x (ORCPT ); Mon, 10 Nov 2008 02:58:53 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:34142 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753353AbYKJH6w (ORCPT ); Mon, 10 Nov 2008 02:58:52 -0500 Date: Mon, 10 Nov 2008 08:58:27 +0100 From: Ingo Molnar To: Grant Grundler Cc: Nobin Mathew , Jiri Slaby , linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, Robert Hancock , Thomas Gleixner , Peter Zijlstra Subject: Re: sharing interrupt between PCI device Message-ID: <20081110075827.GE2093@elte.hu> References: <4910E8AC.7050407@shaw.ca> <8d6898730811042349p19e65556l8e1c851b27758d5@mail.gmail.com> <20081108172716.GA28039@colo.lackof.org> <4915E43E.4010206@gmail.com> <20081108191536.GC28039@colo.lackof.org> <8d6898730811092235u4a41c664vd641d2792dee4c50@mail.gmail.com> <20081110075115.GA13239@colo.lackof.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081110075115.GA13239@colo.lackof.org> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00,DNS_FROM_SECURITYSAGE autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.0 DNS_FROM_SECURITYSAGE RBL: Envelope sender in blackholes.securitysage.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 733 Lines: 19 * Grant Grundler 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/