From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:37653) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SuJY7-0000J4-TF for qemu-devel@nongnu.org; Thu, 26 Jul 2012 04:36:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SuJY2-0003IZ-1N for qemu-devel@nongnu.org; Thu, 26 Jul 2012 04:35:59 -0400 Received: from mx1.redhat.com ([209.132.183.28]:11450) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SuJY1-0003IP-PH for qemu-devel@nongnu.org; Thu, 26 Jul 2012 04:35:53 -0400 Message-ID: <50110163.30209@redhat.com> Date: Thu, 26 Jul 2012 11:35:47 +0300 From: Avi Kivity MIME-Version: 1.0 References: <20120725165948.17260.82862.stgit@bling.home> <50104973.3090302@redhat.com> <1343246026.2229.374.camel@bling.home> In-Reply-To: <1343246026.2229.374.camel@bling.home> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH] vfio: VFIO PCI driver for Qemu List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex Williamson Cc: aik@ozlabs.ru, qemu-devel@nongnu.org, kvm@vger.kernel.org On 07/25/2012 10:53 PM, Alex Williamson wrote: > On Wed, 2012-07-25 at 22:30 +0300, Avi Kivity wrote: >> On 07/25/2012 08:03 PM, Alex Williamson wrote: >> > This adds PCI based device assignment to Qemu using the Linux VFIO >> > userspace driver interface. After setting up VFIO device access, >> > devices can be added to Qemu guests using the vfio-pci device >> > option: >> > >> > -device vfio-pci,host=1:10.1,id=net0 >> > >> > >> >> Let's use the same syntax as for kvm device assignment. Then we can >> fall back on kvm when vfio is not available. We can also have an >> optional parameter kernel-driver to explicitly select vfio or kvm. > > This seems confusing to me, pci-assign already has options like > prefer_msi, share_intx, and configfd that vfio doesn't. I'm sure vfio > will eventually get options that pci-assign won't have. How is a user > supposed to figure out what options are actually available from -device > pci-assign,? Read the documentation. > Isn't this the same as asking to drop all model specific > devices and just use -device net,model=e1000... hey, we've been there > before ;) Thanks, It's not. e1000 is a guest visible feature. vfio and kvm assignment do exactly the same thing, as far as the guest is concerned, just using a different driver. This is more akin to -device virtio-net,vhost=on|off (where we also have a default and a fallback, which wouldn't make sense for model=e1000). -- error compiling committee.c: too many arguments to function