linux-kernel - Re: [PATCH v6 00/27] x86, boot, 64bit: Add support for loading ramdisk and bzImage above 4G

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]

Message-ID: <50CA6918.5060806@zytor.com>
Date:	Thu, 13 Dec 2012 15:47:36 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	Stefano Stabellini <Stefano.Stabellini@...citrix.com>
Subject: Re: [PATCH v6 00/27] x86, boot, 64bit: Add support for loading ramdisk
 and bzImage above 4G

There are obviously good bits to this patchset, but I'm really starting 
to think the "pseudo-linear mode" via a trap handler -- meaning we can 
access all of memory without any extra effort -- makes more sense.  In 
fact, that way we could just build the full page tables without worrying 
about incremental bootstrap, depending on if that is a complexity win or 
not.

Either way, this is for native only: the Xen domain builder or other 
similar entry paths should be setting up page tables that cover all of 
memory; I'm hoping Konrad and Stefano can confirm this.

The only reason to go with another approach I can think of is if it 
makes 32/64-bit unification cleaner.

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