vhost: add cleanup_vqs to do some cleanup stuff

Activate_vqs is used to do the queue preparation before really
running. The virtio-vhost device might need to do some cleanup
to allow a second round activate in the future. How to do the
cleanup is depending on how the vhost virtio devices.

Just add an interface called cleanup_vqs to allow the vhost virtio
devices to do their own cleanup stuff.

BUG=None
TEST=launch Crosvm guest with vhost-net and vsock. Both of them can work
TEST=cargo test -p devices

Change-Id: I2472e79a8b63c9336f886cde55ffef6a78008ad8
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.corp-partner.google.com>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1954172
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>

1 files changed, 8 insertions, 2 deletions

diff --git a/devices/src/virtio/vhost/vsock.rs b/devices/src/virtio/vhost/vsock.rs
index 32f2c99..192e5ce 100644
--- a/devices/src/virtio/vhost/vsock.rs
+++ b/devices/src/virtio/vhost/vsock.rs
@@ -173,8 +173,14 @@ impl VirtioDevice for Vsock {
                                 handle.start().map_err(Error::VhostVsockStart)?;
                                 Ok(())
                             };
-                            let result =
-                                worker.run(queue_evts, QUEUE_SIZES, kill_evt, activate_vqs);
+                            let cleanup_vqs = |_handle: &VhostVsockHandle| -> Result<()> { Ok(()) };
+                            let result = worker.run(
+                                queue_evts,
+                                QUEUE_SIZES,
+                                kill_evt,
+                                activate_vqs,
+                                cleanup_vqs,
+                            );
                             if let Err(e) = result {
                                 error!("vsock worker thread exited with error: {:?}", e);
                             }