From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lpp01m010-f46.google.com ([209.85.215.46]:34796 "EHLO mail-lpp01m010-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965935Ab2FAXHO convert rfc822-to-8bit (ORCPT ); Fri, 1 Jun 2012 19:07:14 -0400 Received: by lahd3 with SMTP id d3so1916378lah.19 for ; Fri, 01 Jun 2012 16:07:13 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <1333968563.5678.19.camel@infinity> <4F89CE43.7040200@snewbury.org.uk> <4F8AA0DC.6010902@snewbury.org.uk> <4F8AB312.7060606@snewbury.org.uk> <4F8B04A4.4070507@snewbury.org.uk> <4F8B0609.8010603@snewbury.org.uk> <4F96770D.2050606@snewbury.org.uk> <4FB227D3.7090002@snewbury.org.uk> <4FB4EE99.10509@snewbury.org.uk> <4FB4F039.2040308@snewbury.org.uk> <4FBA7AEE.3090402@snewbury.org.uk> From: Bjorn Helgaas Date: Fri, 1 Jun 2012 17:06:51 -0600 Message-ID: Subject: Re: PCI resources above 4GB To: Steven Newbury Cc: Yinghai Lu , linux-pci@vger.kernel.org, DRI mailing list Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-pci-owner@vger.kernel.org List-ID: On Tue, May 29, 2012 at 5:19 PM, Bjorn Helgaas wrote: > On Mon, May 21, 2012 at 11:27 AM, Steven Newbury wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 18/05/12 10:08, Yinghai Lu wrote: >>> On Fri, May 18, 2012 at 12:45 AM, Yinghai Lu >>> wrote: >>>> On Thu, May 17, 2012 at 9:36 AM, Yinghai Lu >>>> wrote: >>>>> On Thu, May 17, 2012 at 5:34 AM, Steven Newbury >>>>> wrote: >>>>>> -----BEGIN PGP SIGNED MESSAGE----- Strange, the busn branch >>>>>> is merged with for-pci-res-alloc, but for some reason it >>>>>> isn't working.  Only the bridge is detected, not the devices >>>>>> behind it. >>>>> >>>>> Can you post the boot log ? maybe recently reordering patches >>>>> applying sequence break it. >>>> >>>> Never mind, found the problem. >>> >>> updated for-pci-res-alloc branch. please check it. >>> >> Tested and working fine now. > > Can you attach dmesg logs without Yinghai's patches (where I assume it > doesn't work) and with them (where it *does* work) to the bugzilla?  I > assume https://bugzilla.kernel.org/show_bug.cgi?id=10461 is still the > relevant report. > > I'm confused because I thought your _CRS showed no apertures above > 4GB, and I'm trying to figure out how Yinghai's patches can help if > that's the case. Your _CRS *doesn't* show any apertures above 4GB, but you're booting with "pci=nocrs", so we ignore them anyway. Doing hotplug with "pci=nocrs" is not a supportable proposition. Patches that help in the "pci=nocrs" case might be acceptable, but only if there is clearly no risk to the "pci=use_crs" case.