Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M9xNJ-0002il-J2 for qemu-devel@nongnu.org; Fri, 29 May 2009 04:23:37 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M9xNE-0002gV-Gi for qemu-devel@nongnu.org; Fri, 29 May 2009 04:23:36 -0400 Received: from [199.232.76.173] (port=43646 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M9xNE-0002gQ-7l for qemu-devel@nongnu.org; Fri, 29 May 2009 04:23:32 -0400 Received: from lizzard.sbs.de ([194.138.37.39]:19374) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M9xND-0000s0-9F for qemu-devel@nongnu.org; Fri, 29 May 2009 04:23:31 -0400 Message-ID: <4A1F9B7C.4020201@siemens.com> Date: Fri, 29 May 2009 10:23:24 +0200 From: Jan Kiszka MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Lost interrupts with upstream KVM List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: qemu-devel , kvm-devel 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? TiA, Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux