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 11:46:22 +0200 Message-ID: <4BAB30EE.4020509@redhat.com> References: <1269497376-21903-1-git-send-email-cam@cs.ualberta.ca> 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 To: Cam Macdonell Return-path: Received: from mx1.redhat.com ([209.132.183.28]:2608 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750906Ab0CYJq0 (ORCPT ); Thu, 25 Mar 2010 05:46:26 -0400 In-Reply-To: <1269497376-21903-1-git-send-email-cam@cs.ualberta.ca> Sender: kvm-owner@vger.kernel.org List-ID: 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. -- error compiling committee.c: too many arguments to function