[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4916DB16.2040709@redhat.com>
Date: Sun, 09 Nov 2008 14:44:06 +0200
From: Avi Kivity <avi@...hat.com>
To: Greg KH <greg@...ah.com>
CC: "Fischer, Anna" <anna.fischer@...com>, H L <swdevyid@...oo.com>,
"randy.dunlap@...cle.com" <randy.dunlap@...cle.com>,
"grundler@...isc-linux.org" <grundler@...isc-linux.org>,
"Chiang, Alexander" <achiang@...com>,
"matthew@....cx" <matthew@....cx>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"rdreier@...co.com" <rdreier@...co.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jbarnes@...tuousgeek.org" <jbarnes@...tuousgeek.org>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"mingo@...e.hu" <mingo@...e.hu>
Subject: Re: [PATCH 0/16 v6] PCI: Linux kernel SR-IOV support
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists