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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 01 May 2008 22:01:54 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Robert Hancock <hancockr@...w.ca>
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) ?

Robert Hancock wrote:
>>
>> 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..

There is no doubt ACPI is critical.  Using E820 is good practice too, 
though.  Windows actually uses (only) one of several methods, depending 
on which HAL it chooses to use.

	-hpa
--
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/