From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm@xmission.com (Eric W. Biederman) Subject: Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3) Date: Tue, 07 Nov 2006 10:49:36 -0700 Message-ID: References: <20061107171143.GU27140@parisc-linux.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20061107171143.GU27140@parisc-linux.org> (Matthew Wilcox's message of "Tue, 7 Nov 2006 10:11:43 -0700") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: Matthew Wilcox Cc: Andrew Morton , len.brown@intel.com, Thierry Vignaud , linux-pm@osdl.org, Ernst Herzberg , Aaron Durbin , Alex Romosan , openib-general@openib.org, Andi Kleen , linux-ide@vger.kernel.org, Linus Torvalds , oprofile-list@lists.sourceforge.net, Jens Axboe , Adrian Bunk , linux-pci@atrey.karlin.mff.cuni.cz, Elimar Riesebieter , discuss@x86-64.org, Komuro , Jeff Chua , Tim Chen , phil.el@wanadoo.fr, gregkh@suse.de, neilb@cse.unsw.edu.au, Christian , Linux Kernel Mailing List , linux-acpi@vger.kernel.org, mingo@redhat.com, nfs@lists.sourc List-Id: linux-pm@vger.kernel.org Matthew Wilcox writes: > On Wed, Nov 08, 2006 at 12:57:03AM +0800, Jeff Chua wrote: >> 2) this fails ... >> = >> e0000000-efffffff : 0000:00:02.0 >> f0000000-ffffffff : PCI MMCONFIG 0 >> fed00000-fed003ff : HPET 0 > > Heh, no kidding ... > > num_buses =3D pci_mmcfg_config[i].end_bus_number - > pci_mmcfg_config[i].start_bus_number + 1; > res->start =3D pci_mmcfg_config[i].base_address; > res->end =3D res->start + (num_buses << 20) - 1; > res->flags =3D IORESOURCE_MEM | IORESOURCE_BUSY; > insert_resource(&iomem_resource, res); > > So if we have 256 busses assigned, then we request 256MB and, well, > there's no room for anyone else. This code was added by Andi in commit > de09bddb9d6f96785be470c832b881e6d72d589f > > Hopefully he'll have a good idea how to restrict it. Given your "working" > resource map, it seems like it should be limited to 16MB (and thus 16 bus= ses). > But how to figure that out? Sounds like you need to find the current maximum bus number in use. A little more sophisticated would look at where the next reserved region be= gins. ACPI might have some of that information as well. Although I'm not certain where we you are coming from. = If you don't have to worry about device hotplug getting the current maximum= bus number should be all you need. Eric