From: Jamie Lokier <jamie@shareable.org>
To: Cam Macdonell <cam@cs.ualberta.ca>
Cc: Avi Kivity <avi@redhat.com>, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: [PATCH v3 0/2] Inter-VM shared memory PCI device
Date: Fri, 26 Mar 2010 01:32:15 +0000 [thread overview]
Message-ID: <20100326013215.GF19308@shareable.org> (raw)
In-Reply-To: <8286e4ee1003251117o74486dck813a47cee54b2d6d@mail.gmail.com>
Cam Macdonell wrote:
> An irqfd can only trigger a single vector in a guest. Right now I
> only have one eventfd per guest. So ioeventfd/irqfd restricts the
> current implementation to a single vector that a guest can trigger.
> Without irqfd, eventfds can be used like registers a write the number
> of the vector they want to trigger, but as you point out it is racy.
It's not racy if you use a pipe instead of eventfd. :-)
Actually, why not? A byte pipe between guests would be more versatile.
Could it even integrate with virtio-serial, somehow?
-- Jamie
next prev parent reply other threads:[~2010-03-26 1:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 6:08 [PATCH v3 0/2] Inter-VM shared memory PCI device Cam Macdonell
2010-03-25 6:08 ` [PATCH v3 1/2] Support adding a file to qemu's ram allocation Cam Macdonell
2010-03-25 6:08 ` [PATCH v3 2/2] Inter-VM shared memory PCI device Cam Macdonell
2010-03-25 9:04 ` [PATCH v3 0/2] " Avi Kivity
2010-03-25 9:21 ` Michael S. Tsirkin
2010-03-25 16:11 ` Cam Macdonell
2010-03-25 9:26 ` Markus Armbruster
2010-03-25 9:37 ` Avi Kivity
2010-03-25 16:50 ` Cam Macdonell
2010-03-25 17:02 ` Avi Kivity
2010-03-25 17:35 ` Cam Macdonell
2010-03-25 17:48 ` Avi Kivity
2010-03-25 18:17 ` Cam Macdonell
2010-03-25 21:10 ` Avi Kivity
2010-03-25 23:05 ` Cam Macdonell
2010-03-26 15:56 ` Avi Kivity
2010-03-26 1:32 ` Jamie Lokier [this message]
2010-03-26 15:52 ` [Qemu-devel] " Cam Macdonell
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=20100326013215.GF19308@shareable.org \
--to=jamie@shareable.org \
--cc=avi@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 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.