Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756395Ab0DIW4r (ORCPT ); Fri, 9 Apr 2010 18:56:47 -0400 Received: from rcsinet11.oracle.com ([148.87.113.123]:64039 "EHLO rcsinet11.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755920Ab0DIW4m (ORCPT ); Fri, 9 Apr 2010 18:56:42 -0400 Message-ID: <4BBFB032.4050503@oracle.com> Date: Fri, 09 Apr 2010 15:54:42 -0700 From: Yinghai User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100228 SUSE/3.0.3-1.1.1 Thunderbird/3.0.3 MIME-Version: 1.0 To: "H. Peter Anvin" CC: Andy Isaacson , guenter.roeck@ericsson.com, Linus Torvalds , Bjorn Helgaas , Thomas Gleixner , Ingo Molnar , "linux-pci@vger.kernel.org" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , Thomas Renninger Subject: Re: [PATCH] x86: Reserve legacy VGA MMIO area for x86_64 as well as x86_32 References: <201004071705.07176.bjorn.helgaas@hp.com> <4BBD13C3.2060404@oracle.com> <201004091004.39857.bjorn.helgaas@hp.com> <4BBF5987.3010100@zytor.com> <4BBF626A.3060800@oracle.com> <4BBF70BC.3080809@zytor.com> <1270839357.1477.758.camel@groeck-laptop> <4BBF863B.1060806@oracle.com> <20100409222103.GA11130@hexapodia.org> <4BBFA9BF.60608@oracle.com> <20100409223532.GC11130@hexapodia.org> <4BBFADDB.6000508@zytor.com> In-Reply-To: <4BBFADDB.6000508@zytor.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Source-IP: acsmt355.oracle.com [141.146.40.155] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090206.4BBFB086.00E0:SCFMA4539814,ss=1,fgs=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1524 Lines: 37 On 04/09/2010 03:44 PM, H. Peter Anvin wrote: > On 04/09/2010 03:35 PM, Andy Isaacson wrote: >> [ 2.267740] pci 0000:00:1f.2: BAR 5: assigned [mem 0x000a0000-0x000a07ff] >> [ 2.274701] pci 0000:00:1f.2: BAR 5: set to [mem 0x000a0000-0x000a07ff] (PCI address [0xa0000-0xa07ff] > > Looks like this is something the kernel is assigning to it. It *does* > get marked reserved: > >> [ 0.000000] #6 [000009ec00 - 00000f0000] BIOS reserved > > ... but that doesn't seem to keep the PCI code from assigning anything > there. This is a Very Bad thing in general... if we're assigning > devices to areas marked reserved, we have a huge problem. _CRS report those range are used devices under the peer root bus. and in e820_reserve_resources_late, we are using insert_resource_expand_to_fit() to register E820_RESERVED region. could be that insert_resource_expand_to_fit doesn't work in that case. like in the tree when we have [ 0.704003] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] [ 0.705002] pci_root PNP0A03:00: host bridge window [mem 0x000c0000-0x000effff] [ 0.706002] pci_root PNP0A03:00: host bridge window [mem 0x000f0000-0x000fffff] and then insert_resource... [0x9fec00, 0x100000) it is not inserted to tree properly YH -- 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/