From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jan Kiszka <jan.kiszka@siemens.com>
Subject: VMX: Host NMI triggering on NMI vmexit
Date: Tue, 16 Sep 2008 13:26:41 +0200
Message-ID: <48CF97F1.9090004@siemens.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Cc: Avi Kivity <avi@qumranet.com>, kvm-devel <kvm@vger.kernel.org>
To: "Yang, Sheng" <sheng.yang@intel.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from lizzard.sbs.de ([194.138.37.39]:16780 "EHLO lizzard.sbs.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752580AbYIPL0u (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 16 Sep 2008 07:26:50 -0400
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Sheng,

out of curiosity: vmx_vcpu_run invokes 'int $2' to trigger a host NMI if
the VM exited due to an external NMI event. According to Intel specs I
have, software-triggered NMIs do not block hardware NMIs. So are we
facing the risk to receive another NMI while running the first handler?
Or will the VM be left with the hardware blocking logic armed? Or does
Linux not care about NMI handler re-entrance?

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux