From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: XSA-60 - how to get back to a sane state Date: Mon, 2 Dec 2013 19:43:17 +0000 Message-ID: <529CE2D5.7030805@eu.citrix.com> References: <529CA7250200007800108CB8@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VnZOt-0003ij-2W for xen-devel@lists.xenproject.org; Mon, 02 Dec 2013 19:43:23 +0000 In-Reply-To: <529CA7250200007800108CB8@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , xen-devel Cc: Jinsong Liu , Keir Fraser , Andrew Cooper , Zhenzhong Duan , Donald D Dugger , Jun Nakajima List-Id: xen-devel@lists.xenproject.org On 12/02/2013 02:28 PM, Jan Beulich wrote: > All, > > Jinsong's patches having been in for nearly a month now, but not > being in a shape that would make releasing in 4.4 or backporting to > the older trees desirable, we need to come to a conclusion on > which way to go. Currently it looks like we have three options, but > of course I'll be happy to see other (better!) ones proposed. > > 1) Stay with what we have. > > 2) Revert 86d60e85 ("VMX: flush cache when vmentry back to UC > guest") in its entirety plus, perhaps, the change 62652c00 ("VMX: > fix cr0.cd handling") did to vmx_ctxt_switch_to(). > > 3) Apply the attached patch that Andrew and I have been putting > together, with the caveat that it's still incomplete (see below). > > The latter two are based on the observation that the amount of > cache flushing we do with what is in the master tree right now is > more than what we did prior to that patch series but still > insufficient. Hence the revert would get us back to the earlier > state (and obviously eliminate the performance problems that > were observed when doing too eager flushing), whereas > applying the extra 5th patch would get us closer to a proper > solution. What's missing is a description of the pros and cons of 1 and 2. Do you have any links to threads describing the problem? -George