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

Message-ID: <20080502080303.GQ20451@one.firstfloor.org>
Date:	Fri, 2 May 2008 10:03:03 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Robert Hancock <hancockr@...w.ca>
Cc:	"H. Peter Anvin" <hpa@...or.com>, 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>, lenb@...nel.org
Subject: Re: Why such a big difference in init-time PCI resource call-paths (x86 vs x86_64) ?

> 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..

The usual problem is that they don't use that on older systems
but a different HAL (or XP doesn't run at all on these older systems).
But Linux still wants to run on older systems, ideally without
special settings too.

So if it's done like this it likely needs some date or other heuristic to 
decide if it should trust ACPI or should not. 

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