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  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, 05 Nov 2007 12:31:09 -0800
From:	"H. Peter Anvin" <>
To:	"Eric W. Biederman" <>
CC:	Linus Torvalds <>,
	Linux Kernel Mailing List <>,
	Thomas Gleixner <>,
	Ingo Molnar <>,
	Mikael Petterson <>,
	Jeremy Fitzhardinge <>
Subject: Re: [GIT PULL] x86 setup: correct booting on 486 (revised)

Eric W. Biederman wrote:
>>> However, that being said, doing so is trivial, and it might help some
>>> debugging hack; anything that makes debugging easier is a Good Thing[TM].
>> Yeah. Even if it was just re-using the boot-time stack area temporarily, 
>> just to give code the choice to use a common set of instructions.
> If I had to do it from scratch today I would make the 32-bit entry
> point require a stack, segments and use C calling conventions to pass
> struct boot_params *.
> Besides %esi I'm not really fond of requiring anything in the 32bit
> entrypoint.  At the same time I totally agree that it is always nice
> to provide way more then you need.

Nailing down the interface as hard as possible is a good idea, to avoid 
tying your hands for the future.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists