From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Xen 4.7 Development Update Date: Mon, 01 Feb 2016 05:11:19 -0700 Message-ID: <56AF597702000078000CCEAF@prv-mh.provo.novell.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aQDKI-0004C9-Py for xen-devel@lists.xenproject.org; Mon, 01 Feb 2016 12:11:26 +0000 In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: wei.liu2@citrix.com Cc: xen-devel@lists.xenproject.org, Shuai Ruan List-Id: xen-devel@lists.xenproject.org >>> On 01.02.16 at 11:45, 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... Jan