Dmitry Torokhov 0db8f41245 Ensure we are not holding per-cpu data lock when pausing VCPU ... We may want to issue additional crosvm_pause_vcpu() requests while VCPUs are waiting to be resumed, so we need to make sure we are not holding lock while waiting. TEST=cargo test --features plugin BUG=chromium:800626 Change-Id: Ia74836a567fc565fbd868abdcaa6d0174a4341ad Signed-off-by: Dmitry Torokhov <dtor@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/917426 Reviewed-by: Zach Reizner <zachr@chromium.org>		2018-02-16 15:12:24 -08:00
..
mini_plugin_template.c
plugin.policy
plugin_adder.c	allow non-dirty log memory regions from the plugin process	2018-02-12 22:42:37 -08:00
plugin_dirty_log.c	allow non-dirty log memory regions from the plugin process	2018-02-12 22:42:37 -08:00
plugin_extensions.c	allow plugin to query for KVM extensions	2018-02-12 22:42:40 -08:00
plugin_ioevent.c	allow non-dirty log memory regions from the plugin process	2018-02-12 22:42:37 -08:00
plugin_irqfd.c	allow non-dirty log memory regions from the plugin process	2018-02-12 22:42:37 -08:00
plugin_vcpu_pause.c	Ensure we are not holding per-cpu data lock when pausing VCPU	2018-02-16 15:12:24 -08:00
plugins.rs	Ensure we are not holding per-cpu data lock when pausing VCPU	2018-02-16 15:12:24 -08:00