Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753549Ab2F1Nil (ORCPT ); Thu, 28 Jun 2012 09:38:41 -0400 Received: from mga11.intel.com ([192.55.52.93]:46168 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751645Ab2F1Nij convert rfc822-to-8bit (ORCPT ); Thu, 28 Jun 2012 09:38:39 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208";a="171110192" From: "Liu, Jinsong" To: Jan Beulich , "Auld, Will" CC: "Raj, Ashok" , "Dugger, Donald D" , "Shan, Haitao" , "Nakajima, Jun" , "Li, Susie" , "Luck, Tony" , "Zhang, Xiantao" , "Jiang, Yunhong" , "xen-devel@lists.xensource.com" , "linux-kernel@vger.kernel.org" , Keir Fraser Subject: RE: [xen vMCE RFC V0.2] xen vMCE design Thread-Topic: [xen vMCE RFC V0.2] xen vMCE design Thread-Index: AQHNVRQt1l9vq4iTRyWE8p2SJy8j95cPtZ2g Date: Thu, 28 Jun 2012 13:38:36 +0000 Message-ID: References: <4FEB236C020000780008C392@nat28.tlf.novell.com> <4FEC3B4A020000780008C673@nat28.tlf.novell.com> <4FEC463E020000780008C6A7@nat28.tlf.novell.com> In-Reply-To: <4FEC463E020000780008C6A7@nat28.tlf.novell.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1747 Lines: 38 Jan Beulich wrote: >>>> On 28.06.12 at 11:40, "Liu, Jinsong" wrote: >> So I would like to push new vMCE as quickly as possible. What's the >> timeline of vMCE developing that xen 4.2 could accept? > > Weeks ago, really. See > http://lists.xen.org/archives/html/xen-devel/2012-06/msg01619.html > and follow-ups - we'd really only consider getting the save/restore > interface into forward compatible shape as acceptable. > >> I wonder if we could make major >> components of vMCE done before xen 4.2 timeline, and leave the >> surrounding features and the corner cases done later? > > Unfortunately it's likely going to be even less. However, if split > that way, chances are things could go into e.g. 4.2.1. > > Jan So let's look at current vMCE status first: 1). functionally it work abnormally for guest (but tolerated by some guest like linux/solaris); 2). before xen 4.1 it blocks migration when migrate from big bank to small bank platform; We may try some middle steps, minimal adjusting for xen 4.2 release (to avoid futher compatible issue at xen 4.2.1, 4.3, ...): 1). we don't handle vMCE function bugs, only make sure migration works OK; 2). update vMCE interface to a middle clean status: * remove MCG_CTL (otherwise we have to add this useless MSR at new vMCE); * stick all 1's to MCi_CTL (avoid semantic difference); * for MCG_CAP, clear MCG_CTL_P, limit to 2 banks (otherwise dirty code have to be added at new vMCE); Thoughts? Thanks, Jinsong-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/