From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Williamson Subject: Re: [RFC PATCH] vfio: VFIO PCI driver for Qemu Date: Wed, 25 Jul 2012 13:53:46 -0600 Message-ID: <1343246026.2229.374.camel@bling.home> References: <20120725165948.17260.82862.stgit@bling.home> <50104973.3090302@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, aik@ozlabs.ru, benh@kernel.crashing.org To: Avi Kivity Return-path: Received: from mx1.redhat.com ([209.132.183.28]:10245 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752262Ab2GYTxw (ORCPT ); Wed, 25 Jul 2012 15:53:52 -0400 In-Reply-To: <50104973.3090302@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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,? 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, Alex