linux-kernel - Re: Why such a big difference in init-time PCI resource call-paths (x86 vs x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-id: <481AA095.3010201@shaw.ca>
Date:	Thu, 01 May 2008 23:03:17 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-pci@...ey.karlin.mff.cuni.cz, TJ <linux@...orld.net>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Why such a big difference in init-time PCI resource call-paths
 (x86 vs x86_64) ?

H. Peter Anvin wrote:
> Andi Kleen wrote:
>> On Thu, May 01, 2008 at 11:16:31AM -0700, Jesse Barnes wrote:
>>> On Wednesday, April 30, 2008 9:07 am TJ wrote:
>>>> In preparation for writing a Windows-style PCI resource allocation
>>>> strategy
>>>>
>>>>  - use all e820 gaps for IOMEM resources; top-down allocation -
>>>>
>>>> and thus giving devices with large IOMEM requirements more chance of
>>>> allocation in the 32-bit address space below 4GB (see bugzilla #10461),
>>
>> I tried that some time ago and it turned out that some systems have
>> mappings in holes and don't boot anymore when you fill the holes too 
>> much. But that was only considering e820. if you do this it might work 
>> if you do it really like windows and consider all resources, including 
>> ACPI.
> 
> Yes, considering all possible reservation schemes is really critical 
> here (including the magic knowledge of the legacy region).

FYI, from what I've read, Windows ignores e820 for detecting resource 
reservations and looks at ACPI reservations only (at least if it's 
running in ACPI mode which these days is almost universal). It seems 
Windows really only uses e820 for locating RAM areas..
--
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/