Re: [PATCH v2] Shared memory device with interrupt support

From: Avi Kivity <avi@redhat.com>
To: Gregory Haskins <ghaskins@novell.com>
Cc: Cam Macdonell <cam@cs.ualberta.ca>,
	"Kumar, Venkat" <Venkat.Kumar@lsi.com>,
	"kvm@vger.kernel.org list" <kvm@vger.kernel.org>
Subject: Re: [PATCH v2] Shared memory device with interrupt support
Date: Mon, 18 May 2009 14:38:39 +0300	[thread overview]
Message-ID: <4A1148BF.6060902@redhat.com> (raw)
In-Reply-To: <4A114281.3070209@novell.com>

Gregory Haskins wrote:
> I'll just add that you could tie the irqfd to an iosignalfd to eliminate
> the involvement of qemu on either side as well.  I'm not sure if that
> really works with the design of this particular device (e.g. perhaps
> qemu is needed for other reasons besides signaling), but it is a neat
> demonstration of the flexibility of the newly emerging kvm-eventfd
> interfaces.
>   

If we have an iosignalfd for point-to-point (say, a pio port with the 
guest ID) we can do direct guest-to-guest signalling.  For broadcast or 
multicast, we need to exit to qemu to handle the loop.

-- 
error compiling committee.c: too many arguments to function