From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NuyPQ-0004C5-7i
	for qemu-devel@nongnu.org; Thu, 25 Mar 2010 21:32:24 -0400
Received: from [140.186.70.92] (port=43840 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NuyPN-0004B3-Rs
	for qemu-devel@nongnu.org; Thu, 25 Mar 2010 21:32:22 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <jamie@shareable.org>) id 1NuyPL-0005O6-NJ
	for qemu-devel@nongnu.org; Thu, 25 Mar 2010 21:32:21 -0400
Received: from mail2.shareable.org ([80.68.89.115]:58444)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <jamie@shareable.org>) id 1NuyPL-0005Ny-Ec
	for qemu-devel@nongnu.org; Thu, 25 Mar 2010 21:32:19 -0400
Date: Fri, 26 Mar 2010 01:32:15 +0000
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] Re: [PATCH v3 0/2] Inter-VM shared memory PCI device
Message-ID: <20100326013215.GF19308@shareable.org>
References: <1269497310-21858-1-git-send-email-cam@cs.ualberta.ca>
	<4BAB2736.7020202@redhat.com>
	<8286e4ee1003250950l45cc2883yd4788d20f99ef86c@mail.gmail.com>
	<4BAB9718.3030808@redhat.com>
	<8286e4ee1003251035o75fed405j45b60d496afa66b5@mail.gmail.com>
	<4BABA1F4.3000801@redhat.com>
	<8286e4ee1003251117o74486dck813a47cee54b2d6d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8286e4ee1003251117o74486dck813a47cee54b2d6d@mail.gmail.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Cam Macdonell <cam@cs.ualberta.ca>
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org, qemu-devel@nongnu.org

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