summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/event_analyzing_sample.py
diff options
context:
space:
mode:
authorYishai Hadas <yishaih@nvidia.com>2024-11-13 14:51:59 +0300
committerAlex Williamson <alex.williamson@redhat.com>2024-11-14 02:28:32 +0300
commit6cea64b1db8885b82c226f9f80c2325f39d9d309 (patch)
tree47f23100bb756f422b2ca574ac7b0ba543c45d92 /tools/perf/scripts/python/event_analyzing_sample.py
parent0bbc82e4ec79df437de49d45c512335d97f9c7ce (diff)
downloadlinux-6cea64b1db8885b82c226f9f80c2325f39d9d309.tar.xz
vfio/virtio: Add PRE_COPY support for live migration
Add PRE_COPY support for live migration. This functionality may reduce the downtime upon STOP_COPY as of letting the target machine to get some 'initial data' from the source once the machine is still in its RUNNING state and let it prepares itself pre-ahead to get the final STOP_COPY data. As the Virtio specification does not support reading partial or incremental device contexts. This means that during the PRE_COPY state, the vfio-virtio driver reads the full device state. As the device state can be changed and the benefit is highest when the pre copy data closely matches the final data we read it in a rate limiter mode. This means we avoid reading new data from the device for a specified time interval after the last read. With PRE_COPY enabled, we observed a downtime reduction of approximately 70-75% in various scenarios compared to when PRE_COPY was disabled, while keeping the total migration time nearly the same. Signed-off-by: Yishai Hadas <yishaih@nvidia.com> Link: https://lore.kernel.org/r/20241113115200.209269-7-yishaih@nvidia.com Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions