]> xenbits.xensource.com Git - people/liuw/libxenctrl-split/libvirt.git/commit
The policy kit and HAL node device drivers both require a
authorDaniel P. Berrange <berrange@redhat.com>
Thu, 19 Apr 2012 14:34:35 +0000 (15:34 +0100)
committerDaniel Berrange <berrange@dhcp-159.gsslab.fab.redhat.com>
Thu, 19 Apr 2012 16:03:10 +0000 (17:03 +0100)
commit2223ea984cb9484cdcdcb8732c04072e84b40dd4
treecdd7e734b4790ed631434846a732608ab81028ed
parent7c26343bc38e9fb91dcb0911cb851592d03e0721
The policy kit and HAL node device drivers both require a
DBus connection. The HAL device code further requires that
the DBus connection is integrated with the event loop and
provides such glue logic itself.

The forthcoming FirewallD integration also requires a
dbus connection with event loop integration. Thus we need
to pull the current event loop glue out of the HAL driver.

Thus we create src/util/virdbus.{c,h} files. This contains
just one method virDBusGetSystemBus() which obtains a handle
to the single shared system bus instance, with event glue
automagically setup.
15 files changed:
configure.ac
daemon/Makefile.am
daemon/libvirtd.c
daemon/remote.c
include/libvirt/virterror.h
po/POTFILES.in
src/Makefile.am
src/libvirt_dbus.syms [deleted file]
src/libvirt_private.syms
src/node_device/node_device_hal.c
src/rpc/virnetserver.c
src/rpc/virnetserver.h
src/util/virdbus.c [new file with mode: 0644]
src/util/virdbus.h [new file with mode: 0644]
src/util/virterror.c