All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm-devel <kvm@vger.kernel.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: Lost interrupts with upstream KVM
Date: Fri, 29 May 2009 10:23:24 +0200	[thread overview]
Message-ID: <4A1F9B7C.4020201@siemens.com> (raw)

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

             reply	other threads:[~2009-05-29  8:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29  8:23 Jan Kiszka [this message]
2009-05-29  8:26 ` Lost interrupts with upstream KVM Gleb Natapov
2009-05-29 13:08 ` Gleb Natapov
2009-05-29 14:52   ` Jan Kiszka
2009-05-29 16:20     ` Gleb Natapov
2009-05-29 16:46       ` Jan Kiszka
2009-05-29 16:54         ` Gleb Natapov
2009-05-29 17:01           ` Jan Kiszka
2009-05-29 17:19             ` Gleb Natapov
2009-05-29 17:26               ` Jan Kiszka
2009-05-29 17:31                 ` Gleb Natapov
2009-05-29 17:35                   ` Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A1F9B7C.4020201@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.