From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: Lost interrupts with upstream KVM Date: Fri, 29 May 2009 11:26:41 +0300 Message-ID: <20090529082641.GA28542@redhat.com> References: <4A1F9B7C.4020201@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm-devel , qemu-devel To: Jan Kiszka Return-path: Received: from mx2.redhat.com ([66.187.237.31]:52154 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754383AbZE2I0o (ORCPT ); Fri, 29 May 2009 04:26:44 -0400 Content-Disposition: inline In-Reply-To: <4A1F9B7C.4020201@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: 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? > Will look at it. Thanks. -- Gleb.