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
| ||
|
Date: Sat, 18 Apr 2009 17:32:17 -0700 From: "H. Peter Anvin" <hpa@...or.com> To: Linus Torvalds <torvalds@...ux-foundation.org> CC: Yinghai Lu <yinghai@...nel.org>, Ingo Molnar <mingo@...e.hu>, Jesse Barnes <jbarnes@...tuousgeek.org>, Andrew Morton <akpm@...ux-foundation.org>, Thomas Gleixner <tglx@...utronix.de>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, linux-pci@...r.kernel.org, yannick.roehlly@...e.fr Subject: Re: [PATCH] x86/pci: make pci_mem_start to be aligned only -v4 Linus Torvalds wrote: >> >> 00000100-000973ff : System RAM >> 00097400-0009ffff : reserved >> 000a0000-000bffff : PCI Bus #00 >> 000c0000-000cffff : pnp 00:0c >> 000e0000-000fffff : pnp 00:0c >> 00100000-b7f9ffff : System RAM >> 00200000-00c68f6b : Kernel code >> 00c68f6c-01332f7f : Kernel data >> 015a6000-01fcaa57 : Kernel bss >> 20000000-23ffffff : GART >> b7fa0000-b7fadfff : RAM buffer >> b7fae000-b7faffff : System RAM >> b7fb0000-b7fbdfff : ACPI Tables >> b7fbe000-b7feffff : ACPI Non-volatile Storage >> b7ff0000-b7ffffff : reserved > > Hmm. That looks correct to me. We filled in that odd area between > b7fa0000-b7fadfff that went unmentioned in the e820 tables. > > And that _is_ a really odd hole. I wonder what it is all about. But the > approach does seem to have done the right thing. > Looks to me as through the BIOS rounded the end of available memory to a 64K boundary after subtracting the ACPI storage. That might have been done to work around an OS loader bug somewhere. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- 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