aboutsummaryrefslogtreecommitdiff
path: root/balloon.c
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2016-10-21 22:48:15 +0200
committerMichael S. Tsirkin <mst@redhat.com>2016-10-30 20:06:21 +0200
commitfa283a4a8be621d9be88c87458355aa4800b731c (patch)
treef9cabceff7a5e47b8aee4a2909c4faaa0c97c44c /balloon.c
parented08a2a0ba165bfa3d520126eed340c803308321 (diff)
downloadqemu-fa283a4a8be621d9be88c87458355aa4800b731c.zip
qemu-fa283a4a8be621d9be88c87458355aa4800b731c.tar.gz
qemu-fa283a4a8be621d9be88c87458355aa4800b731c.tar.bz2
virtio: inline virtio_queue_set_host_notifier_fd_handler
Of the three possible parameter combinations for virtio_queue_set_host_notifier_fd_handler: - assign=true/set_handler=true is only called from virtio_device_start_ioeventfd - assign=false/set_handler=false is called from set_host_notifier_internal but it only does something when reached from virtio_device_stop_ioeventfd_impl; otherwise there is no EventNotifier set on qemu_get_aio_context(). - assign=true/set_handler=false is called from set_host_notifier_internal, but it is not doing anything: with the new start_ioeventfd and stop_ioeventfd methods, there is never an EventNotifier set on qemu_get_aio_context() at this point. This is enforced by the assertion in virtio_bus_set_host_notifier. Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'balloon.c')
0 files changed, 0 insertions, 0 deletions