Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754768Ab0AZSXO (ORCPT ); Tue, 26 Jan 2010 13:23:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754726Ab0AZSXN (ORCPT ); Tue, 26 Jan 2010 13:23:13 -0500 Received: from hera.kernel.org ([140.211.167.34]:56307 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753995Ab0AZSXM (ORCPT ); Tue, 26 Jan 2010 13:23:12 -0500 Message-ID: <4B5F32A9.7090105@kernel.org> Date: Tue, 26 Jan 2010 10:21:29 -0800 From: Yinghai Lu User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091130 SUSE/3.0.0-1.1.1 Thunderbird/3.0 MIME-Version: 1.0 To: Linus Torvalds CC: Bjorn Helgaas , "Rafael J. Wysocki" , Jeff Garrett , Linux Kernel Mailing List , Kernel Testers List , Linux PCI , Jesse Barnes , Myron Stowe , Matthew Garrett , Ingo Molnar Subject: Re: [Bug #15124] PCI host bridge windows ignored (works with pci=use_crs) References: <20100126071912.GA7543@jgarrett.org> <201001261348.59508.rjw@sisk.pl> <201001261032.37053.bjorn.helgaas@hp.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1639 Lines: 36 On 01/26/2010 10:16 AM, Linus Torvalds wrote: > > > On Tue, 26 Jan 2010, Bjorn Helgaas wrote: >> >> which IS big enough, and we know the bridge is in fact forwarding the >> [mem 0xd0000000-0xdfffffff 64bit pref] region, because the Radeon works >> when Jeff boots with "pci=use_crs". > > I bet it's a subtractive decode thing. Sure, it could be just another > undocumented range register (does anybody have the datasheet for that > thing?) but Intel tends to often have subtractive decode. > > That system in question has three PCI express root ports, but two of them > have IO and memory disabled according to the lspci info. So maybe it's as > simple as that "I/O Hub PCI Express Root Port 7" just catching anything > that nobody else does, and the single IOH host chip doing the same? > >> I think we should remove intel_bus.c before .33. It's breaking boxes >> and we don't know how to fix it. Even if we do find out how to fix it, >> I think we should move toward using _CRS instead, because that's what >> Windows uses and it's an easy way for the firmware to tell us about >> platform quirks. > > I suspect that for 33 it is indeed best to just revert. But somebody is > bound to have information on how the actual hardware works. Yinghai? I have asked intel if there is any bit that could be enabled the routing. there is no info about for their documentations. Yinghai -- 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/