From: Andi Kleen <ak@suse.de>
To: virtualization@lists.osdl.org
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Chris Wright <chrisw@sous-sol.org>,
xen-devel@lists.xensource.com,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 17/24] Xen-paravirt_ops: avoid having a bad selector in %gs during context switch
Date: Wed, 21 Feb 2007 23:10:02 +0100 [thread overview]
Message-ID: <200702212310.02218.ak@suse.de> (raw)
In-Reply-To: <20070221205323.770169136@goop.org>
> /*
> + * Temporary hack: zero gs now that we've saved it so that Xen
> + * doesn't try to reload the old value after changing the GDT
> + * during the context switch. This can go away once Xen has
> + * been taught to only reload %gs when it absolutely must.
> + */
> + loadsegment(gs, 0);
Sorry, but i don't really want that unconditionally in the context switch.
Adding a paravirt ops for it would be also ugly. Can Xen be fixed?
-Andi
next parent reply other threads:[~2007-02-21 22:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070221205254.169835700@goop.org>
[not found] ` <20070221205323.770169136@goop.org>
2007-02-21 22:10 ` Andi Kleen [this message]
2007-02-21 22:14 ` [patch 17/24] Xen-paravirt_ops: avoid having a bad selector in %gs during context switch Jeremy Fitzhardinge
2007-02-21 22:16 ` Keir Fraser
2007-02-21 23:25 ` [Xen-devel] " Zachary Amsden
2007-02-21 23:29 ` Jeremy Fitzhardinge
[not found] ` <20070221205322.869165491@goop.org>
2007-02-21 22:15 ` [patch 05/24] Xen-paravirt_ops: Add pagetable accessors to pack and unpack pagetable entries Andi Kleen
2007-02-21 22:20 ` Jeremy Fitzhardinge
2007-02-21 23:20 ` Rusty Russell
2007-02-21 23:27 ` [Xen-devel] " Jeremy Fitzhardinge
[not found] ` <20070221205323.842917348@goop.org>
2007-02-22 3:10 ` [patch 18/24] Xen-paravirt_ops: Some generic early printk & boot console fixups Andrew Morton
2007-02-22 5:48 ` Jeremy Fitzhardinge
2007-02-22 8:33 ` Gerd Hoffmann
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=200702212310.02218.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox