From: ebiederm@xmission.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Rusty Russell <rusty@rustcorp.com.au>, Andi Kleen <ak@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i386: always clear bss
Date: Fri, 04 May 2007 11:05:17 -0600 [thread overview]
Message-ID: <m1ejlwr036.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <463B5643.1040204@zytor.com> (H. Peter Anvin's message of "Fri, 04 May 2007 08:50:27 -0700")
"H. Peter Anvin" <hpa@zytor.com> writes:
> Jeremy Fitzhardinge wrote:
>>
>> Yes, that's more or less the same code, aside from using 0x40(%esi) as a
>> stack. Would that be OK here?
>>
>
> I saw the 0x40(%esi) stack stuff, and I'm utterly puzzled by it. There
> is no reason one can't set up %esp to point to a hunk in ordinary memory
> and use it?
That is what we are doing, remind me to make certain we have this
field of the boot protocol documented as permanently reserved for
this.
This comes from the relocatable kernel patches where we run the
kernel where the bootloader chooses to put it assuming we are >= 1M.
The problem is that we don't have any IP relative data access
instructions, we don't have a stack, and so the only valid address
that we know is valid is %esi. Once we compute where we are running
we can setup a base address register and a stack and everything is
easy, but the bootstrap to figure out where we are is just a little
tricky.
Eric
next prev parent reply other threads:[~2007-05-04 17:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 8:21 Jeremy Fitzhardinge
2007-05-04 11:46 ` Eric W. Biederman
2007-05-04 14:57 ` Jeremy Fitzhardinge
2007-05-04 15:22 ` Eric W. Biederman
2007-05-04 15:26 ` Jeremy Fitzhardinge
2007-05-04 15:45 ` Eric W. Biederman
2007-05-04 15:50 ` H. Peter Anvin
2007-05-04 17:05 ` Eric W. Biederman [this message]
2007-05-04 17:08 ` H. Peter Anvin
2007-05-04 17:15 ` Eric W. Biederman
2007-05-04 17:26 ` H. Peter Anvin
2007-05-04 19:00 ` Eric W. Biederman
2007-05-04 19:03 ` H. Peter Anvin
2007-05-04 23:17 ` H. Peter Anvin
2007-05-05 1:45 ` Eric W. Biederman
2007-05-05 1:49 ` H. Peter Anvin
2007-05-05 2:11 ` 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=m1ejlwr036.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®