From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M9xQQ-0004XR-2O for qemu-devel@nongnu.org; Fri, 29 May 2009 04:26:50 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M9xQL-0004To-CE for qemu-devel@nongnu.org; Fri, 29 May 2009 04:26:49 -0400 Received: from [199.232.76.173] (port=47204 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M9xQL-0004Tb-4h for qemu-devel@nongnu.org; Fri, 29 May 2009 04:26:45 -0400 Received: from mx2.redhat.com ([66.187.237.31]:43328) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M9xQK-0002Rs-HL for qemu-devel@nongnu.org; Fri, 29 May 2009 04:26:44 -0400 Date: Fri, 29 May 2009 11:26:41 +0300 From: Gleb Natapov Message-ID: <20090529082641.GA28542@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: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: qemu-devel , kvm-devel 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.