public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 11:57:15 -0700	[thread overview]
Message-ID: <m1bsvlauic.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).

Nope you rely on cs & ds as well.  cs is just a duh the codes running
so it must be valid.  But ds is needed for lgdt.

> > I can tell you don't have real hardware.  The non obviousness

I need to retract this a bit.  You are still building a compressed image,
and the code in the boot/compressed/head.S remains unchanged and loads
segment registers, so it works by luck.  If you didn't build a
compressed image you would be in trouble.
 
> Current code definitely works fine on the simnow simulator so if current code
> shouldn't work because it's buggy then at least the simulator is sure buggy as
> well (and that isn't going to be the case as its behaviour is in full sync with
> the specs as far I can see).

Add a target for a noncompressed image and then build.  It should be
interesting to watch.
> 
> > So while you load the gdt before you set a segment register later,
> > which is good the more important part was still missed.
> 
> Sorry but I don't see the missing part. Are you sure you're not missing this
> part of the x86-64 specs?

Nope because what I was complaining about is in 32 bit mode. :)

> 	Data and Stack Segments:
> 
> 	In 64-bit mode, the contents of the ES, DS, and SS segment registers
> 	are ignored. All fields (base, limit, and attribute) in the
> 	corresponding segment descriptor registers (hidden part) are also
> 	ignored.

Hmm.  I'll have to look and see if FS & GS are also ignored.

> 	Address calculations in 64-bit mode that reference the ES, DS, or SS
> 	segments, are treated as if the segment base is zero.  Rather than
> 	perform limit checks, the processor instead checks that all
> 	virtual-address references are in canonical form.

Cool I like this bit.  The segments are finally dead.

> > O.k. on monday I'll dig up my patch and that clears this up.
> 
> Sure, go ahead if you weren't missing that basic part of the long mode specs.
> Thanks.

Nope.  Though I suspect we should do the switch to 64bit mode in
setup.S and not have these issues pollute head.S at all.

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/

  parent reply	other threads:[~2000-11-12 19:05 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 [this message]
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
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=m1bsvlauic.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