From: Gleb Natapov <gleb@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm-devel <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: Lost interrupts with upstream KVM
Date: Fri, 29 May 2009 19:54:18 +0300 [thread overview]
Message-ID: <20090529165418.GA917@redhat.com> (raw)
In-Reply-To: <4A201177.2090103@siemens.com>
On Fri, May 29, 2009 at 06:46:47PM +0200, Jan Kiszka wrote:
> Gleb Natapov wrote:
> > On Fri, May 29, 2009 at 04:52:41PM +0200, Jan Kiszka wrote:
> >> Gleb Natapov wrote:
> >>> 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?
> >>>>
> >>> In kvm_cpu_exec() after calling kvm_arch_pre_run() env->exit_request is
> >>> tested and function can exit without calling kvm_vcpu_ioctl(KVM_RUN).
> >>> Can you check if this what happens in your case?
> >> This path is executed quite frequently here. No obvious correlation with
> >> the lost IRQ.
> >>
> > If kvm_arch_pre_run() injected interrupt kvm_vcpu_ioctl(KVM_RUN) have to
> > be executed before injecting another interrupt, so if on the fist call
> > of kvm_cpu_exec() kvm_arch_pre_run() injected interrupt, but
> > kvm_vcpu_ioctl(KVM_RUN) was not executed because of env->exit_request
> > and on the next kvm_cpu_exec() other interrupt is injected the previous
> > one will be lost.
>
> ...and kvm_run->ready_for_interrupt_injection is not updated either in
> that case, right? That makes be wonder if KVM_INTERRUPT shouldn't better
> return an error in case the queue is full already.
>
If kvm_vcpu_ioctl(KVM_RUN) is called, but exit happens before interrupt
is injected kvm_run->ready_for_interrupt_injection should be update to
reflect that fact.
--
Gleb.
next prev parent reply other threads:[~2009-05-29 16:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 8:23 [Qemu-devel] Lost interrupts with upstream KVM Jan Kiszka
2009-05-29 8:26 ` [Qemu-devel] " 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 [this message]
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=20090529165418.GA917@redhat.com \
--to=gleb@redhat.com \
--cc=jan.kiszka@siemens.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).