From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: [PATCH 08/13] kvm: x86: Inject pending MCE events on state writeback Date: Thu, 17 Feb 2011 16:17:27 -0200 Message-ID: <20110217181727.GA12721@amt.cnet> References: <56bf7460c65f7fc5c89fa9673b880a556b99e0fc.1297758211.git.jan.kiszka@siemens.com> <20110217163534.GB10918@amt.cnet> <4D5D558B.10406@siemens.com> <20110217175559.GA12113@amt.cnet> <4D5D6343.6060508@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Avi Kivity , "kvm@vger.kernel.org" , "qemu-devel@nongnu.org" , Huang Ying , Hidetoshi Seto , Jin Dongming To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:45884 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752645Ab1BQSoI (ORCPT ); Thu, 17 Feb 2011 13:44:08 -0500 Content-Disposition: inline In-Reply-To: <4D5D6343.6060508@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, Feb 17, 2011 at 07:04:51PM +0100, Jan Kiszka wrote: > >>> Should not manipulate mp_state of a running vcpu (should only do that > >>> for migration when vcpu is stopped), since its managed by the kernel, > >>> for irqchip case. > >> > >> Not for asynchronously injected MCEs. The target CPU would simply > >> oversleep them. MCEs are not in the scope of the in-kernel irqchip. > > > > Pending MCE exception could break out of in-kernel halt emulation. > > Can't follow. What do you mean? That the kernel already takes care? I > didn't find a trace, so I added that code. Nevermind. This is rare and "halted -> running" transition in userspace is harmless.