From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Lost interrupts with upstream KVM Date: Fri, 29 May 2009 10:23:24 +0200 Message-ID: <4A1F9B7C.4020201@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: kvm-devel , qemu-devel To: Gleb Natapov Return-path: Received: from lizzard.sbs.de ([194.138.37.39]:19430 "EHLO lizzard.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756224AbZE2IXr (ORCPT ); Fri, 29 May 2009 04:23:47 -0400 Sender: kvm-owner@vger.kernel.org List-ID: 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