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: Thu, 07 Aug 2008 18:19:19 -0700 From: "H. Peter Anvin" <hpa@...nel.org> To: Zachary Amsden <zach@...are.com> CC: Jeremy Fitzhardinge <jeremy@...p.org>, Alok Kataria <akataria@...are.com>, "torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>, Ingo Molnar <mingo@...e.hu>, the arch/x86 maintainers <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH]Fix broken VMI in 2.6.27-rc.. Zachary Amsden wrote: > > Using my interplanetary ideas, linking the fixmap at runtime would allow > optimal placement of the fixmap, any hypervisor areas, vmalloc, and > pkmap space. That might allow one to increase the amount of lowmem > available for direct mapping depending on some platform variables such > as hypervisor reserved space, physical memory size, APIC present.. those > aren't known until boot time. Actually, NCPUs is a good one, since we > require atomic kmap space dependent on NCPUs, which could be given back > to linear memory map. > > That might actually be more worthwhile than link time fixed addresses. > Yeah, but that's a huge project. -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/
Powered by blists - more mailing lists