xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Sarah Newman <srn@prgmr.com>
To: xen-devel@lists.xen.org
Cc: "Crawford, Luke" <lsc@prgmr.com>
Subject: Re: [PATCH] x86/fpu: CR0.TS should be set before trap into PV guest's #NM exception handle
Date: Wed, 27 Nov 2013 15:35:21 -0800	[thread overview]
Message-ID: <529681B9.4010503@prgmr.com> (raw)
In-Reply-To: <52967C45.3030506@prgmr.com>


> Note the comment close to the beginning - the fact that CR0.TS
> is clear at exception handler entry is actually part of the PV ABI,
> i.e. by altering hypervisor behavior here you break all forward
> ported kernels.
> 
> Nevertheless I agree that there is an issue, but this needs to be
> fixed on the Linux side (hence adding the Linux maintainers to Cc);
> this issue was introduced way back in 2.6.26 (before that there
> was no allocation on that path). It's not clear though whether
> using GFP_ATOMIC for the allocation would be preferable over
> stts() before calling the allocation function (and clts() if it
> succeeded), or whether perhaps to defer the stts() until we
> actually know the task is being switched out. It's going to be an
> ugly, Xen-specific hack in any event.
> 
> Jan

This is a serious bug.  Unfortunately not all of us have the option of updating our guests if/when
such a fix is made to Linux.

How about a per domU + xen command line configuration option to implement Zhu's changes that is
disabled by default?  I'm willing to try to implement it.

       reply	other threads:[~2013-11-27 23:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52967C45.3030506@prgmr.com>
2013-11-27 23:35 ` Sarah Newman [this message]
2013-11-29  9:42   ` [PATCH] x86/fpu: CR0.TS should be set before trap into PV guest's #NM exception handle Jan Beulich
2013-11-30  0:16     ` Sarah Newman
2013-12-02  8:34       ` Jan Beulich
2013-12-02  9:58         ` Luke S. Crawford
2013-12-02 10:04           ` Jan Beulich
2013-12-02 10:25             ` Luke S. Crawford

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=529681B9.4010503@prgmr.com \
    --to=srn@prgmr.com \
    --cc=lsc@prgmr.com \
    --cc=xen-devel@lists.xen.org \
    /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;
as well as URLs for NNTP newsgroup(s).