All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH, RFC] x86: make the GDT per-CPU
Date: Thu, 11 Sep 2008 13:42:49 +0100	[thread overview]
Message-ID: <48C92E69.76E4.0078.0@novell.com> (raw)
In-Reply-To: <48C92AF7.76E4.0078.0@novell.com>

>>> "Jan Beulich" <jbeulich@novell.com> 11.09.08 14:28 >>>
>>> Keir Fraser <keir.fraser@eu.citrix.com> 11.09.08 12:54 >>>
>>Firstly, we don't really need the LDT and TSS GST slots to be always valid.
>>Actually we always initialise the slot immediately before LTR or LLDT. So we
>>could even have per-CPU LDT and TSS initialisation share a single slot.
>>Then, with the extra reserved page, we'd be good for nearly 512 CPUs.
>
>No, this would break 32-bits at least: The GDT entry for the selector
>loaded into TR must remain a valid, busy TSS descriptor for the whole
>lifetime of the system. So it can't be shared with the LDT. But even for
>64-bits I would fear using the same GDT slot for both LDT and GDT
>loading.

Actually, there's a second aspect here, too (again for 32-bits): As a
follow-up patch I'm planning to make the double fault TSS per-CPU, too.
This wasn't as simple with the global GDT as it would be with the per-CPU
one.

Jan

  parent reply	other threads:[~2008-09-11 12:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10 14:35 [PATCH, RFC] x86: make the GDT per-CPU Jan Beulich
2008-09-11 10:54 ` Keir Fraser
2008-09-11 12:28   ` Jan Beulich
2008-09-11 12:35     ` Jan Beulich
2008-09-11 12:42     ` Jan Beulich [this message]
2008-09-11 13:15       ` Keir Fraser

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=48C92E69.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=keir.fraser@eu.citrix.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 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.