public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander van Heukelum <heukelum@mailshack.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	sct@redhat.com, ak@suse.de, herbert@gondor.apana.org.au,
	xen-devel@lists.xensource.com
Subject: Re: [PATCH] shorten the x86_64 boot setup GDT to what the comment says
Date: Thu, 9 Nov 2006 16:44:36 +0100	[thread overview]
Message-ID: <20061109154436.GA31954@mailshack.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0611091016100.6250@gandalf.stny.rr.com>

On Thu, Nov 09, 2006 at 10:18:53AM -0500, Steven Rostedt wrote:
> Hmm, Andi,
> 
> Should this be more like what is done in x86? Although this isn't a major
> bug or anything, would it be cleaner. For example doing:
> 
> @@ -836,11 +836,15 @@ gdt:
>         .word   0x9200                          # data read/write
>         .word   0x00CF                          # granularity = 4096, 386
>                                                 #  (+5th nibble of limit)
> +gdt_end:
> +       .align  4
> +
> +       .word   0                               # alignment byte
>  idt_48:
>         .word   0                               # idt limit = 0
>         .word   0, 0                            # idt base = 0L
>  gdt_48:
> -       .word   0x8000                          # gdt limit=2048,
> +       .word   gdt_end - gdt - 1               # gdt limit=2048,
>                                                 #  256 GDT entries
> 
>         .word   0, 0                            # gdt base (filled in
> 
> instead?

Hi!

Maybe you should consider 16-byte aligning the gdt table too, like
i386 does? It doesn't hurt, and as per the comment in the i386-file
"16 byte aligment is recommended by intel."

Greetings,
	Alexander van Heukelum

> If so, I can send you another patch that does this. Will need to test it
> first.
> 
> -- Steve

  reply	other threads:[~2006-11-09 15:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09  3:01 [PATCH] shorten the x86_64 boot setup GDT to what the comment says Steven Rostedt
2006-11-09 13:13 ` Andi Kleen
2006-11-09 15:31   ` [Xen-devel] " Jan Beulich
2006-11-09 13:31     ` Andi Kleen
2006-11-09 14:54 ` Alexander van Heukelum
2006-11-09 15:18   ` Steven Rostedt
2006-11-09 15:44     ` Alexander van Heukelum [this message]
2006-11-09 13:33       ` Andi Kleen
2006-11-09 18:31         ` Alexander van Heukelum
2006-11-10 14:01           ` Andi Kleen
2006-11-10 15:46             ` Alexander van Heukelum
2006-11-12 13:47               ` Alexander van Heukelum
2006-11-11  5:17             ` [PATCH] make x86_64 boot gdt size exact (like x86) Steven Rostedt
2006-11-11  6:42               ` Andi Kleen
2006-11-13 15:37                 ` Steven Rostedt
2006-11-13 16:47                   ` 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=20061109154436.GA31954@mailshack.com \
    --to=heukelum@mailshack.com \
    --cc=ak@suse.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sct@redhat.com \
    --cc=xen-devel@lists.xensource.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