From: Avi Kivity Subject: Re: [PATCH 0/16 v6] PCI: Linux kernel SR-IOV support Date: Sun, 09 Nov 2008 14:44:06 +0200 Message-ID: <4916DB16.2040709@redhat.com> References: <20081106154351.GA30459@kroah.com> <894107.30288.qm@web45108.mail.sp1.yahoo.com> <20081106164919.GA4099@kroah.com> <0199E0D51A61344794750DC57738F58E5E26F996C4@GVW1118EXC.americas.hpqcorp.net> <20081106180354.GA17429@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Fischer, Anna" , H L , "randy.dunlap@oracle.com" , "grundler@parisc-linux.org" , "Chiang, Alexander" , "matthew@wil.cx" , "linux-pci@vger.kernel.org" , "rdreier@cisco.com" , "linux-kernel@vger.kernel.org" , "jbarnes@virtuousgeek.org" , "virtualization@lists.linux-foundation.org" , "kvm@vger.kernel.org" , "mingo@elte.hu" To: Greg KH Return-path: In-Reply-To: <20081106180354.GA17429@kroah.com> Sender: linux-pci-owner@vger.kernel.org List-Id: kvm.vger.kernel.org Greg KH wrote: > It's that "second" part that I'm worried about. How is that going to > happen? Do you have any patches that show this kind of "assignment"? > > For kvm, this is in 2.6.28-rc. Note there are two ways to assign a device to a guest: - run the VF driver in the guest: this has the advantage of best performance, but requires pinning all guest memory, makes live migration a tricky proposition, and ties the guest to the underlying hardware. - run the VF driver in the host, and use virtio to connect the guest to the host: allows paging the guest and allows straightforward live migration, but reduces performance, and hides any features not exposed by virtio from the guest. -- error compiling committee.c: too many arguments to function