From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
herbert@gondor.apana.org.au, xen-devel@lists.xensource.com,
"LKML" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] Re: [PATCH] shorten the x86_64 boot setup GDT to what the comment says
Date: Thu, 9 Nov 2006 14:31:44 +0100 [thread overview]
Message-ID: <200611091431.44792.ak@suse.de> (raw)
In-Reply-To: <455357C9.76E4.0078.0@novell.com>
On Thursday 09 November 2006 16:31, Jan Beulich wrote:
> >>> Andi Kleen <ak@suse.de> 09.11.06 14:13 >>>
> >>
> >> Stephen Tweedie has written up a patch to fix the Xen side and will be
> >> submitting that to those folks. But that doesn't excuse the GDT limit
> >> being a magnitude too big.
> >
> >Added thanks
>
> Once at this - why not set it to the *correct* value, just like i386 does,
> and update the comment at once? Namely, why would you expect to
> never run into the original problem again if there are still possible
> selectors pointing into invalid, yet within limits parts of the GDT?
Ok I will use an offset.
-Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@suse.de>
To: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com, herbert@gondor.apana.org.au,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Re: [PATCH] shorten the x86_64 boot setup GDT to what the comment says
Date: Thu, 9 Nov 2006 14:31:44 +0100 [thread overview]
Message-ID: <200611091431.44792.ak@suse.de> (raw)
In-Reply-To: <455357C9.76E4.0078.0@novell.com>
On Thursday 09 November 2006 16:31, Jan Beulich wrote:
> >>> Andi Kleen <ak@suse.de> 09.11.06 14:13 >>>
> >>
> >> Stephen Tweedie has written up a patch to fix the Xen side and will be
> >> submitting that to those folks. But that doesn't excuse the GDT limit
> >> being a magnitude too big.
> >
> >Added thanks
>
> Once at this - why not set it to the *correct* value, just like i386 does,
> and update the comment at once? Namely, why would you expect to
> never run into the original problem again if there are still possible
> selectors pointing into invalid, yet within limits parts of the GDT?
Ok I will use an offset.
-Andi
next prev parent reply other threads:[~2006-11-09 15:34 UTC|newest]
Thread overview: 21+ 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 13:13 ` Andi Kleen
2006-11-09 15:31 ` [Xen-devel] " Jan Beulich
2006-11-09 15:31 ` Jan Beulich
2006-11-09 13:31 ` Andi Kleen [this message]
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
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-11 6:42 ` Andi Kleen
2006-11-13 15:37 ` Steven Rostedt
2006-11-13 16:47 ` Andi Kleen
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=200611091431.44792.ak@suse.de \
--to=ak@suse.de \
--cc=herbert@gondor.apana.org.au \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.