From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v3 1/1] Shared memory uio_pci driver Date: Thu, 25 Mar 2010 18:35:07 +0200 Message-ID: <4BAB90BB.5030401@redhat.com> References: <1269497376-21903-1-git-send-email-cam@cs.ualberta.ca> <4BAB30EE.4020509@redhat.com> <8286e4ee1003250924q7cca5e71u8b8b7c6d8b785eb8@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org, "Michael S. Tsirkin" To: Cam Macdonell Return-path: Received: from mx1.redhat.com ([209.132.183.28]:4162 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752970Ab0CYQfL (ORCPT ); Thu, 25 Mar 2010 12:35:11 -0400 In-Reply-To: <8286e4ee1003250924q7cca5e71u8b8b7c6d8b785eb8@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: 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. It >> 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. What > would MSI support for UIO look like? An 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. Similar to ioeventfd, but instead of mapping a doorbell to an eventfd, it maps a real MSI to an eventfd. 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