From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] KVM: x86: Rework request for immediate exit
Date: Thu, 2 May 2013 22:20:39 -0300
Message-ID: <20130503012039.GD5467@amt.cnet>
References: <517CCE8E.6010805@web.de>
 <20130428082951.GD30504@redhat.com>
 <517CE2EC.5010901@web.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Gleb Natapov <gleb@redhat.com>, kvm <kvm@vger.kernel.org>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	"Ren, Yongjie" <yongjie.ren@intel.com>
To: Jan Kiszka <jan.kiszka@web.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:56903 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1760561Ab3ECBVH (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 2 May 2013 21:21:07 -0400
Content-Disposition: inline
In-Reply-To: <517CE2EC.5010901@web.de>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Sun, Apr 28, 2013 at 10:50:52AM +0200, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> The VMX implementation of enable_irq_window raised
> KVM_REQ_IMMEDIATE_EXIT after we checked it in vcpu_enter_guest. This
> caused infinite loops on vmentry. Fix it by letting enable_irq_window
> signal the need for an immediate exit via its return value and drop
> KVM_REQ_IMMEDIATE_EXIT.
> 
> This issue only affects nested VMX scenarios.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Please rebase against "KVM: x86: Account for failing enable_irq_window
for NMI window request".