Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753818AbXIPUGf (ORCPT ); Sun, 16 Sep 2007 16:06:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752277AbXIPUG2 (ORCPT ); Sun, 16 Sep 2007 16:06:28 -0400 Received: from gate.crashing.org ([63.228.1.57]:55080 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752192AbXIPUG1 (ORCPT ); Sun, 16 Sep 2007 16:06:27 -0400 Subject: Re: [PATCH]PCI:disable resource decode in PCI BAR detection From: Benjamin Herrenschmidt To: Robert Hancock Cc: Ivan Kokshaysky , Greg KH , Matthew Wilcox , Shaohua Li , lkml , linux-pci , Andrew Morton In-Reply-To: <46EA00DA.6010704@shaw.ca> References: <46EA00DA.6010704@shaw.ca> Content-Type: text/plain Date: Sun, 16 Sep 2007 22:06:16 +0200 Message-Id: <1189973176.6403.20.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1039 Lines: 26 On Thu, 2007-09-13 at 21:32 -0600, Robert Hancock wrote: > > If we do encounter other devices that choke on having the BAR > disabled > during probing then we can add additional quirk logic, but we haven't > run into anything like that yet. Well... if the device needs to be accessed to service an interrupt then you do have a problem. For example... the PIC :-) Problem is.. it's not practical nor really feasible generally to have IRQs off on all CPUs during PCI probing neither... Unless we define that the initial boot time probing is "special", and the first pass that actually probes devices (and doesn't muck around with the sysfs hierarchy etc...) can be run in a special context with all interrupt servicing disabled on the PIC, though that will require some arch support. Ben. - 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/