From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrea Arcangeli <andrea@suse.de>
Cc: Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
Tigran Aivazian <tigran@veritas.com>,
"H. Peter Anvin" <hpa@transmeta.com>,
Max Inux <maxinux@bigfoot.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: bzImage ~ 900K with i386 test11-pre2
Date: 12 Nov 2000 12:20:19 -0700 [thread overview]
Message-ID: <m17l69atfw.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0011111644110.1036-100000@saturn.homenet> <m1ofzmcne5.fsf@frodo.biederman.org> <20001112122910.A2366@athlon.random> <m1k8a9badf.fsf@frodo.biederman.org> <20001112163705.A4933@athlon.random>
In-Reply-To: Andrea Arcangeli's message of "Sun, 12 Nov 2000 16:37:05 +0100"
Andrea Arcangeli <andrea@suse.de> writes:
> On Sun, Nov 12, 2000 at 06:14:36AM -0700, Eric W. Biederman wrote:
> > x86-64 doesn't load the segment registers at all before use.
>
> Yes, before switching to 64bit long mode we never do any data access. We do a
> stack access to clear eflags only while we still run in legacy mode with paging
> disabled and so we only rely on ss to be valid when the bootloader jumps at
> 0x100000 for executing the head.S code (and not anymore on the gdt_48 layout).
Actually it just occurred to me that this stack assess is buggy. You haven't
set up a stack yet so. Only the boot/compressed/head.S did and that location isn't
safe to use.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-12 19:28 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 23:37 bzImage ~ 900K with i386 test11-pre2 Robert Lynch
2000-11-10 23:47 ` H. Peter Anvin
2000-11-11 2:25 ` Max Inux
2000-11-11 3:03 ` H. Peter Anvin
2000-11-11 5:28 ` Chmouel Boudjnah
2000-11-11 11:27 ` Max Inux
2000-11-11 11:28 ` Jan Niehusmann
2000-11-11 11:38 ` bzImage ~ 900K with i386 test11-pre2, I stand corrected Max Inux
2000-11-11 13:49 ` bzImage ~ 900K with i386 test11-pre2 James A. Sutherland
2000-11-11 20:08 ` H. Peter Anvin
2000-11-11 11:36 ` Tigran Aivazian
2000-11-11 11:38 ` Tigran Aivazian
2000-11-11 11:52 ` Max Inux
2000-11-11 14:42 ` Andrea Arcangeli
2000-11-11 14:51 ` Tigran Aivazian
2000-11-11 16:26 ` Andrea Arcangeli
2000-11-11 16:46 ` Tigran Aivazian
2000-11-11 18:47 ` Andrea Arcangeli
2000-11-11 19:35 ` Eric W. Biederman
2000-11-12 11:29 ` Andrea Arcangeli
2000-11-12 13:14 ` Eric W. Biederman
2000-11-12 15:37 ` Andrea Arcangeli
2000-11-12 15:44 ` Andi Kleen
2000-11-12 16:33 ` Andrea Arcangeli
2000-11-12 18:57 ` Eric W. Biederman
2000-11-12 19:33 ` Andi Kleen
2000-11-16 17:43 ` Eric W. Biederman
2000-11-12 22:30 ` Andrea Arcangeli
2000-11-12 19:20 ` Eric W. Biederman [this message]
2000-11-12 23:03 ` Andrea Arcangeli
2000-11-11 20:09 ` H. Peter Anvin
2000-11-12 16:22 ` Andrea Arcangeli
2000-11-11 16:05 ` Andrzej Krzysztofowicz
2000-11-11 17:27 ` Jeff Garzik
2000-11-14 14:02 ` Werner Almesberger
2000-11-11 5:47 ` Peter Samuelson
2000-11-11 14:30 ` Andi Kleen
2000-11-11 15:43 ` Thomas Köhler
2000-11-11 18:03 ` Robert Lynch
2000-11-11 18:30 ` Andi Kleen
2000-11-11 18:57 ` Robert Lynch
2000-11-11 20:35 ` Andi Kleen
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=m17l69atfw.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=andrea@suse.de \
--cc=hpa@transmeta.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxinux@bigfoot.com \
--cc=tigran@aivazian.fsnet.co.uk \
--cc=tigran@veritas.com \
/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