Re: [PATCH 6/6 v3] PCI: document the change

On Tue, Oct 14, 2008 at 12:18:40PM +0800, Dong, Eddie wrote:

Matthew Wilcox wrote:

quoted

On Tue, Oct 14, 2008 at 10:14:35AM +0800, Yu Zhao wrote:

quoted

As Eddie said, we have two problems here:
1) User has to set device specific parameters of a VF
when he wants to use this VF with KVM (assign this
device to KVM guest). In this case, 
VF driver is not loaded in the host environment. So
operations which 
are implemented as driver callback (e.g.
set_mac_address()) are not supported.

I suspect what you want to do is create, then configure
the device in the host, then assign it to the guest.

That is not true. Rememver the created VFs will be destroyed no matter
for PF power event or error recovery conducted reset.
So what we want is:

Config, create, assign, and then deassign and destroy and then
recreate...

Yes, but my point is this all happens in the _host_, not in the _guest_.

Sorry can u explain a little bit more? The SR-IOV patch won't define
what kind of entries should be created or not, we leave network
subsystem to decide what to do. Same for disk subsstem etc.

No entries should be created.  This needs to be not SR-IOV specific.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."