Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261684AbVDZRPQ (ORCPT ); Tue, 26 Apr 2005 13:15:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261680AbVDZRPQ (ORCPT ); Tue, 26 Apr 2005 13:15:16 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:19328 "HELO iolanthe.rowland.org") by vger.kernel.org with SMTP id S261684AbVDZROi (ORCPT ); Tue, 26 Apr 2005 13:14:38 -0400 Date: Tue, 26 Apr 2005 13:14:38 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Grant Grundler cc: Alexander Nyberg , Greg KH , Amit Gud , , , , , , USB development list Subject: Re: [PATCH] PCI: Add pci shutdown ability In-Reply-To: <20050426163734.GF2612@colo.lackof.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 992 Lines: 22 On Tue, 26 Apr 2005, Grant Grundler wrote: > Agreed - but this is a different problem than "shutting down IRQs". > My point was arch specific code knows how to mask all IRQs. > irq_disable() is expected to work regardless of what state the > driver is in. On kexec "reboot", kernel drivers can unmask IRQs > as they normally would during initialization. No? One has to be careful when talking about enabling/disable IRQs, because there are (at least) two choke points: one on the device and one on the computer's interrupt controller. Masking IRQs takes place on the controller, but I was talking about stopping interrupt requests at their source on the device. It's the only way to avoid problems when IRQ lines are shared. Alan Stern - 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/