qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cam Macdonell <cam@cs.ualberta.ca>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: UIO interrupts being lost
Date: Fri, 25 Jun 2010 13:32:40 +0300	[thread overview]
Message-ID: <20100625103240.GB16321@redhat.com> (raw)
In-Reply-To: <AANLkTinBUBSDM-SQXt64CGrF2TBcGPoJQKPojk5N9FCY@mail.gmail.com>

On Thu, Jun 24, 2010 at 05:43:15PM -0600, Cam Macdonell wrote:
> Hi Michael,
> 
> I'm trying to write a uio driver for my shared memory device for KVM
> and I'm running into a situation where several interrupts in quick
> succession are not all triggering the callback function in my kernel
> UIO driver, say 2 out of 5.  My driver does not set the Interrupt
> Disable bit and if it helps, I'm using MSI-X interrupts.  Even without
> the interrupt disable bit set, is there still a window where
> successive interrupts can be lost if they arrive too quickly?
> 
> Thanks,
> Cam

Yes, I think so: if an interrupt is delivered when
ISR is running, it gets queued, but a second one
gets lost.

A queueing mechanism is necessary to avoid losing
information, e.g. virtio implements exactly that.
Why don't you reuse virtio for signalling?

If I understand what Anthony said correctly,
he objected to the specific implementation,
not to the idea of reusing virtio spec and code.

-- 
MST

           reply	other threads:[~2010-06-25 17:52 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <AANLkTinBUBSDM-SQXt64CGrF2TBcGPoJQKPojk5N9FCY@mail.gmail.com>]

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=20100625103240.GB16321@redhat.com \
    --to=mst@redhat.com \
    --cc=cam@cs.ualberta.ca \
    --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).