linux-kernel - Re: [PATCH] reserve_early end-of-conventional-memory to 1MB

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:	Mon, 25 Feb 2008 13:17:34 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Alexander van Heukelum <heukelum@...tmail.fm>
CC:	Ingo Molnar <mingo@...e.hu>, Andi Kleen <ak@...e.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Alexander van Heukelum <heukelum@...lshack.com>
Subject: Re: [PATCH] reserve_early end-of-conventional-memory to 1MB

Alexander van Heukelum wrote:
> 
> Hello hpa,
> 
> I failed to find a comment referring to 0x413 or int 0x12 in
> arch/x86/kernel. I do know the comment in Documentation/i386/boot.txt,
> however, suggesting that "INT 12h" _should_ be used, but that it would
> be pointless for zImage and old bzImage kernels, because they _have_
> to be started from 0x90000 anyway. New bzImage kernels do not have
> this limitation, and smart bootloaders simply put them at much
> lower addresses, like 0x40000. (I know: you know.) My point is just
> that the argument not to use 0x413 in the bootloader is not valid
> for this case.
> 

OK, let me see if I can dig up the comment I thought I found at one 
point, and maybe found out the history behind it.  Either that, or find 
out that my memory is faulty ;)

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