From: ebiederm@xmission.com (Eric W. Biederman)
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
"H. Peter Anvin" <hpa@zytor.com>, 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 09:22:47 -0600 [thread overview]
Message-ID: <m13b2csjeg.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <463B49F0.401@goop.org> (Jeremy Fitzhardinge's message of "Fri, 04 May 2007 07:57:52 -0700")
Jeremy Fitzhardinge <jeremy@goop.org> writes:
> BTW, I should have marked this as an RFC comment, rather than an actual
> submission. We don't need it for .22.
>
>> NAK.
>>
>> Skipping the segment register load is likely fine.
>> Supporting V!=P at startup_32 is not.
>>
>
> Why?
>
>> Assuming that we have a stack at startup_32 is not.
>>
>> If you want to figure out where the kernel is loaded you can do
>> (from arch/i386/boot/head.S)
>>
>
> Yes, that's more or less the same code, aside from using 0x40(%esi) as a
> stack. Would that be OK here?
Using 0x40 as a stack would be ok.
There are issues with CONFIG_RELOCATABLE and V!=P that I'm not
comfortable with yet, because we can't tell the difference.
Eric
next prev parent reply other threads:[~2007-05-04 15:23 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 [this message]
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
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=m13b2csjeg.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®