From: Linus Torvalds Subject: Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3) Date: Wed, 8 Nov 2006 10:52:05 -0800 (PST) Message-ID: References: <20061107171143.GU27140@parisc-linux.org> <200611080839.46670.ak@suse.de> <20061108122237.GF27140@parisc-linux.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Cc: Andrew Morton , len.brown@intel.com, Thierry Vignaud , Matthew Wilcox , Ernst Herzberg , Aaron Durbin , Alex Romosan , openib-general@openib.org, Andi Kleen , linux-ide@vger.kernel.org, oprofile-list@lists.sourceforge.net, Jens Axboe , Adrian Bunk , linux-pci@atrey.karlin.mff.cuni.cz, Elimar Riesebieter , discuss@x86-64.org, linux-pm@osdl.org, Komuro , Jeff Chua , Tim Chen , phil.el@wanadoo.fr, gregkh@suse.de, neilb@cse.unsw.edu.au, Linux Kernel Mailing List , linux-acpi@vger.kernel.org, mingo@redhat.com, nfs@lists.sourceforge.net, cpufreq@lists.linux.o Return-path: To: "Eric W. Biederman" In-Reply-To: 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 List-ID: On Wed, 8 Nov 2006, Eric W. Biederman wrote: > = > The implementations I have seen, I believe have all been on bridges and > the maximum size is actually generated from the bus number below the brid= ge. Hmm. It might be possible to first set up the MMCONFIG thing for the = minimum range, then read the bus numbers from the host bridge on that bus, = and then expand the mmconfig range if necessary. Because pretty much ANYTHING is better than trusting the BIOS tables. That said, I'd really be a _lot_ more confident about it if we were to be = able to read the values from the hardware itself some way. There's = obviously a chicken-and-egg issue on mmcfg configuration, but it's one = that the BIOS startup code also has, so I assume that there is a solution = to that somewhere. Linus