From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NvCBT-0002OU-PP for qemu-devel@nongnu.org; Fri, 26 Mar 2010 12:14:56 -0400 Received: from [140.186.70.92] (port=41974 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NvCBS-0002OC-Fe for qemu-devel@nongnu.org; Fri, 26 Mar 2010 12:14:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NvCBQ-0008JV-VI for qemu-devel@nongnu.org; Fri, 26 Mar 2010 12:14:54 -0400 Received: from mail-px0-f203.google.com ([209.85.216.203]:57061) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NvCBQ-0008JC-Od for qemu-devel@nongnu.org; Fri, 26 Mar 2010 12:14:52 -0400 Received: by pxi41 with SMTP id 41so1584860pxi.23 for ; Fri, 26 Mar 2010 09:14:50 -0700 (PDT) MIME-Version: 1.0 Sender: camm@ualberta.ca In-Reply-To: <4BAB90BB.5030401@redhat.com> References: <1269497376-21903-1-git-send-email-cam@cs.ualberta.ca> <4BAB30EE.4020509@redhat.com> <8286e4ee1003250924q7cca5e71u8b8b7c6d8b785eb8@mail.gmail.com> <4BAB90BB.5030401@redhat.com> Date: Fri, 26 Mar 2010 10:14:49 -0600 Message-ID: <8286e4ee1003260914u5e6ceee2pf0c00590de182fb6@mail.gmail.com> From: Cam Macdonell Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] Re: [PATCH v3 1/1] Shared memory uio_pci driver List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, "Michael S. Tsirkin" On Thu, Mar 25, 2010 at 10:35 AM, Avi Kivity wrote: > On 03/25/2010 06:24 PM, Cam Macdonell wrote: >> >>> There is now a generic PCI 2.3 driver that can handle all PCI devices. >>> =A0It >>> doesn't support MSI, but if we add MSI support then it can be used >>> without >>> the need for a specialized driver. >>> >> >> Agreed, I'd be happy to use the generic driver if MSI is there. =A0What >> would MSI support for UIO look like? =A0An array of "struct uio_irq" for >> the different vectors? >> > > I'm not familiar with the uio internals, but for the interface, an ioctl(= ) > on the fd to assign an eventfd to an MSI vector. =A0Similar to ioeventfd,= but > instead of mapping a doorbell to an eventfd, it maps a real MSI to an > eventfd. uio will never support ioctls. Maybe irqcontrol could be extended? > > That would be very useful for device assignment: we can pick up a uio > device, map its vectors, and give them to a guest. > > > -- > error compiling committee.c: too many arguments to function > >