From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752711Ab0FNSXd (ORCPT ); Mon, 14 Jun 2010 14:23:33 -0400 Received: from rcsinet10.oracle.com ([148.87.113.121]:53891 "EHLO rcsinet10.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751837Ab0FNSXa (ORCPT ); Mon, 14 Jun 2010 14:23:30 -0400 Message-ID: <4C167357.6040901@oracle.com> Date: Mon, 14 Jun 2010 11:22:15 -0700 From: Yinghai Lu User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100317 SUSE/3.0.4-1.1.1 Thunderbird/3.0.4 MIME-Version: 1.0 To: Jesse Barnes CC: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Bjorn Helgaas , Graham Ramsey , linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, Robert Richter , Harald Welte , Joseph Chan , Jiri Slaby , Hidetoshi Seto , Andrew Morton , Dominik Brodowski Subject: Re: [PATCH -v2] x86, pci: Handle fallout pci devices with peer root bus References: <4BF40014.30303@ntlworld.com> <201005201108.07040.bjorn.helgaas@hp.com> <201006021058.57361.bjorn.helgaas@hp.com> <201006111549.05164.bjorn.helgaas@hp.com> <4C12C189.50201@oracle.com> <4C166B4F.90308@oracle.com> <20100614111425.7fb143f9@virtuousgeek.org> In-Reply-To: <20100614111425.7fb143f9@virtuousgeek.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Auth-Type: Internal IP X-Source-IP: acsinet15.oracle.com [141.146.126.227] X-CT-RefId: str=0001.0A090205.4C167385.00F4:SCFMA922111,ss=1,fgs=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/14/2010 11:14 AM, Jesse Barnes wrote: > On Mon, 14 Jun 2010 10:47:59 -0700 > Yinghai Lu wrote: > >> >> Graham bisected >> | commit 3e3da00c01d050307e753fb7b3e84aefc16da0d0 >> | x86/pci: AMD one chain system to use pci read out res >> >> cause the SND_HDA_INTEL doesn't work anymore. >> >> https://bugzilla.kernel.org/show_bug.cgi?id=16007 >> >> It turns out that his system with via chipset only have one hypertransport >> chain, but does have one extra orphan device 80:01.0 >> >> PCI: Probing PCI hardware (bus 00) >> PCI: Discovered primary peer bus 80 [IRQ] >> >> node 0 link 0: io port [1000, ffffff] >> TOM: 0000000080000000 aka 2048M >> node 0 link 0: mmio [e0000000, efffffff] >> node 0 link 0: mmio [a0000, bffff] >> node 0 link 0: mmio [80000000, ffffffff] >> bus: [00, ff] on node 0 link 0 >> >> Try to make peer root buses to share same mmio/io resources if those peer root >> buses fall into the same bus range. >> >> Also need to update insert_resource to avoid insert same resource two times. > > So 3e3da00c01d050307e753fb7b3e84aefc16da0d0 was supposed to address the > case where some laptop RAM ranges ended up incorrect. Would using _CRS > on those machines also address that problem? If so, we should consider > dropping amd_bus.c like we did with intel_bus.c. > > Yinghai, do you still have people from the RAM bug that could test > using _CRS data? I can not find the mail anymore. looks like someone is using one AMD k8 Aruma laptop for firewire development. YH