Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261891AbVEKFdd (ORCPT ); Wed, 11 May 2005 01:33:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261881AbVEKFdd (ORCPT ); Wed, 11 May 2005 01:33:33 -0400 Received: from e32.co.us.ibm.com ([32.97.110.130]:39405 "EHLO e32.co.us.ibm.com") by vger.kernel.org with ESMTP id S261891AbVEKFdb (ORCPT ); Wed, 11 May 2005 01:33:31 -0400 Date: Wed, 11 May 2005 11:03:27 +0530 From: Vivek Goyal To: Alan Stern Cc: Alexander Nyberg , Greg KH , Amit Gud , linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz, akpm@osdl.org, jgarzik@pobox.com, cramerj@intel.com, USB development list , Maneesh Soni Subject: Re: [PATCH] PCI: Add pci shutdown ability Message-ID: <20050511053327.GA28791@in.ibm.com> Reply-To: vgoyal@in.ibm.com References: <1114462323.983.45.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1189 Lines: 25 > I looked into the possibility of having the PCI core disable interrupt > generation and DMA on each new device as it is discovered. Unfortunately > there is no dependable, universal way to do this for IRQs. (A notable gap > in the original PCI specification, IMHO.) PCI specification 2.3 onwards, command register bit 10 can be used for disabling the interrupts from respective device. And the very reason for introducing this bit seems to be to not allow the device issue interrupts until a suitable driver for the device has been loaded. Have a look at following message. http://www.pcisig.com/reflector/msg05302.html Probably this feature can be used to disable the interrupts from the devices and enable these back when respective driver is loaded. This will resolve the problem of drivers not getting initialized in second kernel due to shared interrupts in kdump and reliability of capturing dump can be increased. Thanks Vivek - 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/