[PATCH 0/2] Abstracting device address allocation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



More hypervisors may implement the possibility of specifying device
addresses, so it makes sense to make QEMU-specific code more generic
to be prepared for it.

If this approach will be acceptable, all the other address sets
will be moved from QEMU's private data to domainDef, the
qemu_domain_address.c will shrink in size and the functionality
will be moved to domain_addr.[hc].

Tomasz Flendrich (2):
  Move virtio *Free() functions from domain_addr to domain_conf
  Move vioserialaddrs from QEMU's private data to domainDef

 src/conf/domain_addr.c         | 22 ----------------------
 src/conf/domain_addr.h         | 17 -----------------
 src/conf/domain_conf.c         | 23 +++++++++++++++++++++++
 src/conf/domain_conf.h         | 19 +++++++++++++++++++
 src/libvirt_private.syms       |  3 ++-
 src/qemu/qemu_domain.c         |  1 -
 src/qemu/qemu_domain.h         |  1 -
 src/qemu/qemu_domain_address.c | 20 ++++++++------------
 src/qemu/qemu_hotplug.c        |  9 +++++----
 9 files changed, 57 insertions(+), 58 deletions(-)

-- 
2.7.4 (Apple Git-66)

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list



[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]