From: xen@bugs.xenproject.org
To: George Dunlap <George.Dunlap@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Processed: Re: [PATCH] x86/fpu: CR0.TS should be set before trap into PV guest's #NM exception handler
Date: Thu, 27 Feb 2014 12:30:02 +0000 [thread overview]
Message-ID: <control-reply-1393504202.19606@bugs.xenproject.org> (raw)
In-Reply-To: <CAFLBxZYpV9boJFHyLAk31bS=tYJsKZDNf1e2b+VoOtb7iF+VoQ@mail.gmail.com>
Processing commands for xen@bugs.xenproject.org:
> create ^
Created new bug #40 rooted at `<1383720072-6242-1-git-send-email-gaoyang.zyh@taobao.com>'
Title: `Re: [Xen-devel] [PATCH] x86/fpu: CR0.TS should be set before trap into PV guest's #NM exception handler'
> title it linux pvops: fpu corruption due to incorrect assumptions
Set title for #40 to `linux pvops: fpu corruption due to incorrect assumptions'
> about TS bit after exception under Xen
Command failed: Unknown command `about'. at /srv/xen-devel-bugs/lib/emesinae/control.pl line 455, <GEN1> line 3.
Stop processing here.
Modified/created Bugs:
- 40: http://bugs.xenproject.org/xen/bug/40 (new)
---
Xen Hypervisor Bug Tracker
See http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for information on reporting bugs
Contact xen-bugs-owner@bugs.xenproject.org with any infrastructure issues
next prev parent reply other threads:[~2014-02-27 12:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 6:41 [PATCH] x86/fpu: CR0.TS should be set before trap into PV guest's #NM exception handler Zhu Yanhai
2013-11-06 8:51 ` Jan Beulich
2013-11-06 9:15 ` Zhu Yanhai
2013-11-06 9:28 ` Jan Beulich
2014-02-27 0:04 ` Matt Wilson
2014-02-27 8:00 ` Jan Beulich
2014-02-27 12:46 ` George Dunlap
2014-02-27 12:37 ` David Vrabel
2014-02-27 12:21 ` George Dunlap
2014-02-27 12:30 ` xen [this message]
2015-09-11 16:50 ` Konrad Rzeszutek Wilk
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=control-reply-1393504202.19606@bugs.xenproject.org \
--to=xen@bugs.xenproject.org \
--cc=George.Dunlap@eu.citrix.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 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.