On Mon, Nov 16, 2009 at 04:14:34PM -0500, Dave Allan wrote: > It would be helpful to have an API that exposes the relationship between > SR IOV physical functions (PFs) and virtual functions (VFs). I'm > thinking of implementing three new API calls and adding a small amount > of additional information in the node device pci device capability, as > in the attached patch. Let me know what you think. Do we really need extra APis for this, vs exposing it in the XML ? I'd think we either use the existing parent/child relationship. ie munge a VF's parent link to point to the PF device, or we could just add a new element giving the device name of the physical function. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list