On 02/28/2012 01:14 PM, Laine Stump wrote: > The parent can be any type of device. It defaults to type=none, and a > NULL pointer. The intent is that if a hostdevdef is contained in the > def for a higher level device (e.g. virDomainNetDef), hostdev->parent > will point to the higher level device, and type will be set to that > type of device. This way, during attach and detach of the device, > parent can be checked, and appropriate callouts made to do higher > level device initialization (e.g. setting MAC address). > > Also, although these hostdevs with parents will be added to a domain's > hostdevs list, they will be treated slightly differently when > traversing the list, e.g. virDomainHostdefDefFree for a hostdev that > has a parent doesn't need to be called (and will be a NOP); it will > simply be removed from the list (since the parent device object is in > its own type-specific list, and will be freed from there). > --- > V2: unchanged from V1 > > src/conf/domain_conf.c | 12 ++++++++++-- > src/conf/domain_conf.h | 1 + > 2 files changed, 11 insertions(+), 2 deletions(-) ACK. -- Eric Blake eblake@xxxxxxxxxx +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list