On Thu, Mar 25, 2010 at 10:24:20AM -0600, Cam Macdonell wrote: > On Thu, Mar 25, 2010 at 3:46 AM, Avi Kivity <avi@xxxxxxxxxx> wrote: > > On 03/25/2010 08:09 AM, Cam Macdonell wrote: > >> > >> This patch adds a driver for my shared memory PCI device using the uio_pci > >> interface. The driver has three memory regions. The first memory region > >> is for > >> device registers for sending interrupts. The second BAR is for receiving > >> MSI-X > >> interrupts and the third memory region maps the shared memory. The device > >> only > >> exports the first and third memory regions to userspace. > >> > >> This driver supports MSI-X and regular pin interrupts. Currently, the > >> number of > >> MSI vectors is set to 4 which could be increased, but the driver will work > >> with > >> fewer vectors. If MSI is not available, then regular interrupts will be > >> used. > >> > > > > 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? > > Cam My idea was to supply a way to bind eventfd to a vector. > > > > -- > > error compiling committee.c: too many arguments to function > > > > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
