From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753692AbbLNXRj (ORCPT ); Mon, 14 Dec 2015 18:17:39 -0500 Received: from mga02.intel.com ([134.134.136.20]:5744 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753453AbbLNXRi (ORCPT ); Mon, 14 Dec 2015 18:17:38 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,429,1444719600"; d="scan'208";a="860709144" Date: Mon, 14 Dec 2015 19:17:27 -0500 From: "Raj, Ashok" To: Borislav Petkov Cc: Eduardo Habkost , kvm@vger.kernel.org, Tony Luck , Gong Chen , Gleb Natapov , linux-kernel@vger.kernel.org, qemu-devel@nongnu.org, Andi Kleen , Paolo Bonzini , Ashok Raj Subject: Re: [Qemu-devel] [Patch V2 1/2] x86, mce: Basic support to add LMCE support to QEMU Message-ID: <20151215001726.GA22215@otc-brkl-03.jf.intel.com> References: <1449776482-26070-1-git-send-email-ashok.raj@intel.com> <20151214162356.GA5314@thinpad.lan.raisama.net> <20151214163738.GJ11630@pd.tnic> <20151214191145.GB18012@otc-brkl-03.jf.intel.com> <20151214223716.GK11630@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151214223716.GK11630@pd.tnic> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 14, 2015 at 11:37:16PM +0100, Borislav Petkov wrote: > On Mon, Dec 14, 2015 at 02:11:46PM -0500, Raj, Ashok wrote: > > This is mostly harmless.. since the MCG_CAP space is shared and has no > > conflict between vendors. Also just the CAP being set has no effect. > > Of course it does - we check SER_P in machine_check_poll() and when > I emulate an AMD guest and inject errors into it, error handling is > obviously wrong, see: > > https://lkml.kernel.org/r/20151123150355.GE5134@pd.tnic > I can see how this hurts.. since the poller isn't doing cpu model specific stuff..? in the LMCE case, even if you advertise MCG_LMCE_P in MCG_CAP, the guest kernel wont call intel_init_lmce() only from mce_intel.c.. so the same problem won't happen. but the issue Eduardo mentioned seems like the following. New QEMU_LMCE + New KVM_LMCE + New_GUEST_LMCE - No problem but if you were to migrage the Guest_LMCE to a non-LMCE supported KVM host we could run into an issue.. is this the compatibility issue that you were looking to fix Eduardo? Cheers, Ashok