From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] KVM: nVMX: Do not emulate #UD while in guest mode
Date: Fri, 13 Mar 2015 13:44:57 -0300
Message-ID: <20150313164457.GB16394@amt.cnet>
References: <54FDFAFB.7050901@siemens.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: kvm <kvm@vger.kernel.org>, Paolo Bonzini <pbonzini@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:50928 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752656AbbCMSsM (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 13 Mar 2015 14:48:12 -0400
Content-Disposition: inline
In-Reply-To: <54FDFAFB.7050901@siemens.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Mon, Mar 09, 2015 at 08:56:43PM +0100, Jan Kiszka wrote:
> While in L2, leave all #UD to L2 and do not try to emulate it. If L1 is
> interested in doing this, it reports its interest via the exception
> bitmap, and we never get into handle_exception of L0 anyway.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> 
> Noticed while wondering where the vmmcall of a misconfigured L2 went on
> an Intel box: to nowhere. This bug caused a spurious fixup, and the
> emulator bug did not even let it trigger a vmcall vmexit.

Applied, thanks.