| commit | db8a3772e300c1a656331a92da0785d81667dc81 | |
| author | Greg Kurz <groug@kaod.org> | |
| Fri, 12 Mar 2021 09:22:11 +0000 (12 10:22 +0100) | ||
| committer | Michael S. Tsirkin <mst@redhat.com> | |
| Mon, 22 Mar 2021 14:17:53 +0000 (22 10:17 -0400) | ||
| tree | 92806eb9243a16a19c4042e88be13e11afca1b27 | treesnapshot (tar.gz zip) |
| parent | a7f523c7d114d445c5d83aecdba3efc038e5a692 | commitdiff |
vhost-user: Monitor slave channel in vhost_user_read()
Now that everything is in place, have the nested event loop to monitor
the slave channel. The source in the main event loop is destroyed and
recreated to ensure any pending even for the slave channel that was
previously detected is purged. This guarantees that the main loop
wont invoke slave_read() based on an event that was already handled
by the nested loop.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <20210312092212.782255-7-groug@kaod.org>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Now that everything is in place, have the nested event loop to monitor
the slave channel. The source in the main event loop is destroyed and
recreated to ensure any pending even for the slave channel that was
previously detected is purged. This guarantees that the main loop
wont invoke slave_read() based on an event that was already handled
by the nested loop.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <20210312092212.782255-7-groug@kaod.org>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
| hw/virtio/vhost-user.c | diffblobblamehistory |