From: "H. Peter Anvin" <hpa@zytor.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Mikael Petterson <mikpe@it.uu.se>
Subject: Re: [GIT PULL] x86 setup: correct booting on 486 (revised)
Date: Tue, 06 Nov 2007 10:41:12 -0800 [thread overview]
Message-ID: <4730B548.8050100@zytor.com> (raw)
In-Reply-To: <m1fxzj5ix6.fsf@ebiederm.dsl.xmission.com>
Eric W. Biederman wrote:
>
> I have a hard time believing in discipline when I see the amount of
> not invented here and various oddball mistakes (cause by overlooking
> things) that seems to go on when extending the format. We never
> needed to change the way the command line was passed, and we should
> have kept the longer jump where we had it.
>
The longer jump was never documented, and so didn't exist. There was
definitely no way to rely on it.
The old command-line protocol had some really ugly interactions with the
absolutely insane hoisting code from the pre-2.02 days. I didn't have
enough guts back then to scream and just rip it out, mostly because it
took me a long time to figure out what the heck it really did (as
opposed to what it claimed it did.) That being said, we probably could
have gotten away with leaving the protocol as-is while ripping out the
guts (as I eventually did in the rewrite), even if the old protocol only
had a 16-bit pointer.
> If we are going to through and add an additional pointer to a notes section
> let's please put a jump in there so we can make the header longer as
> we choose.
The problem is that that will only buy us 15 bytes, and eat up 3 (in
practice, 4) of them...
It might be worth doing anyway, as it'd only break the 32-bit entrypoint
users to reorganize struct boot_params.
-hpa
next prev parent reply other threads:[~2007-11-06 18:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 2:16 [GIT PULL] x86 setup: correct booting on 486 (revised) H. Peter Anvin
2007-11-05 3:58 ` H. Peter Anvin
2007-11-05 17:15 ` Linus Torvalds
2007-11-05 17:56 ` H. Peter Anvin
2007-11-05 18:12 ` Linus Torvalds
2007-11-05 18:32 ` H. Peter Anvin
2007-11-05 18:36 ` Linus Torvalds
2007-11-05 20:21 ` Eric W. Biederman
2007-11-05 20:31 ` H. Peter Anvin
2007-11-05 20:51 ` Jeremy Fitzhardinge
2007-11-05 21:06 ` H. Peter Anvin
2007-11-06 0:59 ` Jeremy Fitzhardinge
2007-11-06 1:11 ` H. Peter Anvin
2007-11-06 1:18 ` Jeremy Fitzhardinge
2007-11-06 1:31 ` H. Peter Anvin
2007-11-06 16:17 ` Jeremy Fitzhardinge
2007-11-06 16:27 ` H. Peter Anvin
2007-11-06 16:55 ` Jeremy Fitzhardinge
2007-11-06 17:00 ` H. Peter Anvin
2007-11-06 17:09 ` Eric W. Biederman
2007-11-06 17:57 ` H. Peter Anvin
2007-11-06 18:27 ` Eric W. Biederman
2007-11-06 18:41 ` H. Peter Anvin [this message]
2007-11-06 17:04 ` Eric W. Biederman
2007-11-05 21:14 ` Eric W. Biederman
2007-11-05 21:28 ` H. Peter Anvin
2007-11-05 21:58 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4730B548.8050100@zytor.com \
--to=hpa@zytor.com \
--cc=ebiederm@xmission.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox