[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BBFB032.4050503@oracle.com>
Date: Fri, 09 Apr 2010 15:54:42 -0700
From: Yinghai <yinghai.lu@...cle.com>
To: "H. Peter Anvin" <hpa@...or.com>
CC: Andy Isaacson <adi@...apodia.org>, guenter.roeck@...csson.com,
Linus Torvalds <torvalds@...ux-foundation.org>,
Bjorn Helgaas <bjorn.helgaas@...com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Thomas Renninger <trenn@...e.de>
Subject: Re: [PATCH] x86: Reserve legacy VGA MMIO area for x86_64 as well
as x86_32
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists