Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759522Ab2FUQGQ (ORCPT ); Thu, 21 Jun 2012 12:06:16 -0400 Received: from nat28.tlf.novell.com ([130.57.49.28]:57560 "EHLO nat28.tlf.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756302Ab2FUQGP convert rfc822-to-8bit (ORCPT ); Thu, 21 Jun 2012 12:06:15 -0400 Message-Id: <4FE362C0020000780008B2CD@nat28.tlf.novell.com> X-Mailer: Novell GroupWise Internet Agent 12.0.0 Date: Thu, 21 Jun 2012 17:06:56 +0100 From: "Jan Beulich" To: "Jinsong Liu" Cc: "Ashok Raj" , "Donald D Dugger" , "Haitao Shan" , "Jun Nakajima" , "Tony Luck" , "Will Auld" , "Xiantao Zhang" , "Yunhong Jiang" , "xen-devel@lists.xensource.com" , "linux-kernel@vger.kernel.org" , "Keir Fraser" Subject: Re: [vMCE design RFC] Xen vMCE design References: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 826 Lines: 20 >>> On 20.06.12 at 18:13, "Liu, Jinsong" wrote: > Recently we design xen vMCE as attached. > Please kindly help me to review it, any comments/suggestions are > appreciated. The concept looks quite okay, provided no OS has a problem with the limitations imposed (most notably the restriction to a single reporting bank, particularly in the context of e.g. Linux partly ignoring the first bank under some conditions iirc). As to not needing any migration specific adjustments - what if a migration is in progress when an event needs to be delivered? Jan -- 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/