From: Wei Liu <wei.liu2@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, wei.liu2@citrix.com,
Shuai Ruan <shuai.ruan@linux.intel.com>
Subject: Re: Xen 4.7 Development Update
Date: Mon, 1 Feb 2016 12:19:23 +0000 [thread overview]
Message-ID: <20160201121923.GD10990@citrix.com> (raw)
In-Reply-To: <56AF597702000078000CCEAF@prv-mh.provo.novell.com>
On Mon, Feb 01, 2016 at 05:11:19AM -0700, Jan Beulich wrote:
> >>> On 01.02.16 at 11:45, <wei.liu2@citrix.com> wrote:
> > * xsave/xrtors support
> > - Shuai Ruan
>
> As per
> http://lists.xenproject.org/archives/html/xen-devel/2016-01/msg03264.html
> and even more importantly
> http://lists.xenproject.org/archives/html/xen-devel/2016-01/msg03271.html
> plus the lack of feedback from the original contributor on almost
> any issues with that code (see e.g. also the recent Xen boot
> problems, which lead to
> http://lists.xenproject.org/archives/html/xen-devel/2016-01/msg03742.html
> ) I'm currently viewing this as a candidate for disabling prior to the
> release, so that we (hopefully) won't end up with the same disaster
> we had with the original enabling of xsave. I'll of course be more
> than happy to be convinced that I'm completely off with the above
> issues...
>
FWIW it is near Chinese New Year so we probably won't hear from the
author any time soon.
I will remove it from "completed" section. We still have two months time
to revert those patches, provided they don't stay in the way of other
changes.
Wei.
> Jan
>
next prev parent reply other threads:[~2016-02-01 12:19 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 10:45 Xen 4.7 Development Update Wei Liu
2016-02-01 12:11 ` Jan Beulich
2016-02-01 12:19 ` Wei Liu [this message]
2016-02-02 7:38 ` Shuai Ruan
2016-02-03 8:55 ` Haozhong Zhang
2016-02-03 9:36 ` Han, Huaitong
2016-02-03 12:22 ` Olaf Hering
-- strict thread matches above, loose matches on Subject: below --
2016-02-29 11:17 Wei Liu
2016-02-29 11:44 ` Jan Beulich
2016-02-29 11:50 ` Wei Liu
2016-02-29 13:27 ` Meng Xu
2016-03-01 22:01 ` Dario Faggioli
2016-02-29 15:35 ` Konrad Rzeszutek Wilk
2016-03-01 10:44 ` Wei Liu
2016-03-02 1:26 ` Han, Huaitong
2016-03-02 3:13 ` Wu, Feng
2016-03-02 5:31 ` Haozhong Zhang
2016-03-02 7:40 ` Shuai Ruan
2016-03-02 11:38 ` George Dunlap
2016-03-02 13:32 ` Jan Beulich
2016-03-02 14:07 ` Paul Durrant
2016-03-02 14:20 ` Jan Beulich
2016-03-02 14:29 ` Paul Durrant
2016-03-02 14:43 ` George Dunlap
2016-03-02 15:07 ` Wei Liu
2016-03-02 14:40 ` Xu, Quan
2016-01-04 10:15 Wei Liu
2016-01-05 6:57 ` Chun Yan Liu
2016-01-06 13:52 ` Jan Beulich
2016-01-05 14:15 ` Haozhong Zhang
2016-01-05 14:30 ` Meng Xu
2016-01-05 14:34 ` Wei Liu
2016-01-05 16:03 ` Meng Xu
2016-01-07 5:41 ` Haozhong Zhang
2016-01-07 10:21 ` Andrew Cooper
2016-01-07 11:52 ` Jan Beulich
2015-12-01 10:34 Wei Liu
2015-11-09 16:15 Wei Liu
2015-11-09 16:49 ` Wei Liu
2015-11-10 1:08 ` Xu, Quan
2015-11-10 4:28 ` Juergen Gross
2015-11-11 14:24 ` Anthony PERARD
2015-11-11 14:36 ` Haozhong Zhang
2015-11-25 2:17 ` Han, Huaitong
2015-12-01 11:54 ` Lars Kurth
2015-12-01 12:35 ` Wei Liu
2015-12-01 12:42 ` Ian Campbell
2015-12-01 12:46 ` Wei Liu
2015-12-01 13:32 ` Yong Wang
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=20160201121923.GD10990@citrix.com \
--to=wei.liu2@citrix.com \
--cc=JBeulich@suse.com \
--cc=shuai.ruan@linux.intel.com \
--cc=xen-devel@lists.xenproject.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).