From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MA1ok-00029x-VK
	for qemu-devel@nongnu.org; Fri, 29 May 2009 09:08:15 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MA1og-00028C-0x
	for qemu-devel@nongnu.org; Fri, 29 May 2009 09:08:14 -0400
Received: from [199.232.76.173] (port=58550 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MA1of-000287-Uz
	for qemu-devel@nongnu.org; Fri, 29 May 2009 09:08:09 -0400
Received: from mx2.redhat.com ([66.187.237.31]:33676)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <gleb@redhat.com>) id 1MA1of-0007Ku-96
	for qemu-devel@nongnu.org; Fri, 29 May 2009 09:08:09 -0400
Date: Fri, 29 May 2009 16:08:06 +0300
From: Gleb Natapov <gleb@redhat.com>
Message-ID: <20090529130806.GB28542@redhat.com>
References: <4A1F9B7C.4020201@siemens.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A1F9B7C.4020201@siemens.com>
Subject: [Qemu-devel] Re: Lost interrupts with upstream KVM
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm-devel <kvm@vger.kernel.org>

On Fri, May 29, 2009 at 10:23:24AM +0200, Jan Kiszka wrote:
> Hi Gleb,
> 
> with latest kernel modules, namely beginning with 6bc0a1a235 (Remove
> irq_pending bitmap), I'm loosing interrupts with upstream's KVM support.
> After some bisecting, hair-pulling and a bit meditation I added a
> WARN_ON(kvm_cpu_has_interrupt(vcpu)) to kvm_vcpu_ioctl_interrupt, and it
> actually triggered right before the guest got stuck.
> 
> This didn't trigger with qemu-kvm (and -no-kvm-irqchip) yet but, on the
> other hand, I currently do not see a potential bug in upstream's
> kvm_arch_pre_run. Could you have a look if you can reproduce,
> specifically if this isn't a KVM kernel issue in the end?
> 
In kvm_cpu_exec() after calling kvm_arch_pre_run() env->exit_request is
tested and function can exit without calling kvm_vcpu_ioctl(KVM_RUN).
Can you check if this what happens in your case?

--
			Gleb.