linux-kernel - Re: [GIT PULL] x86 setup: correct booting on 486 (revised)

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, 05 Nov 2007 16:59:47 -0800
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Mikael Petterson <mikpe@...uu.se>
Subject: Re: [GIT PULL] x86 setup: correct booting on 486 (revised)

H. Peter Anvin wrote:
> Jeremy Fitzhardinge wrote:
>> H. Peter Anvin wrote:
>>> Nailing down the interface as hard as possible is a good idea, to
>>> avoid tying your hands for the future. 
>>
>> Erm, I guess I see what you mean, but it comes to the effect of tying
>> your hands now in a specific way, rather than having them tied in an
>> unknown way later on...
>
> Sort of.  The problem is you can frequently not
>
>> But I hadn't noticed the 32-bit boot protocol spec go in.  Unfortunately
>> it isn't useful for booting a pv Xen guest; I just mailed my
>> comments. I hope we can iterate this to something more generally
>> useful before
>> getting too wedded to the current protocol.
>
> I'm not so sure about that.  Xen PV is rather fundamentally a
> different beast, hence the platform field recently added to the protocol.

Hm, OK.  So make this predicated on "hardware subarchitecture == PC".

>
> This is addressed by the "don't reload segments" bit in LOADFLAGS.

OK.

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