Sebastien Boeuf f6eeba781b vmm: Save and restore vCPU states during pause/resume operations ... We need consistency between pause/resume and snapshot/restore operations. The symmetrical behavior of pausing/snapshotting and restoring/resuming has been introduced recently, and we must now ensure that no matter if we're using pause/resume or snapshot/restore features, the resulting VM should be running in the exact same way. That's why the vCPU state is now stored upon VM pausing. The snapshot operation being a simple serialization of the previously saved state. The same way, the vCPU state is now restored upon VM resuming. The restore operation being a simple deserialization of the previously restored state. It's interesting to note that this patch ensures time consistency from a guest perspective, no matter which clocksource is being used. From a previous patch, the KVM clock was saved/restored upon VM pause/resume. We now have the same behavior for TSC, as the TSC from the vCPUs are saved/restored upon VM pause/resume too. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>		2020-06-25 12:01:34 +02:00
..
src	vmm: Save and restore vCPU states during pause/resume operations	2020-06-25 12:01:34 +02:00
Cargo.toml	build(deps): bump signal-hook from 0.1.15 to 0.1.16	2020-06-22 14:09:11 +01:00