From 9260319e7411ff8281700a532caa436f40120ec4 Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Fri, 30 May 2025 16:52:07 +0200 Subject: gitlab scraper: download in toml and text format --- .../target_missing/host_missing/accel_missing/2480 | 29 ++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 gitlab/issues_text/target_missing/host_missing/accel_missing/2480 (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/2480') diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2480 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2480 new file mode 100644 index 000000000..c562db4e1 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2480 @@ -0,0 +1,29 @@ +Two questions about VFIO device live migration +Description of problem: +For my own pcie device, i implement system memory && device memory dirty bitmap track and works well + +use pre-copy mode live migration by the way. + +first question: +- for system memory dirty bitmap sync, notice that last sync will come early than i expected + read qemu code and found qemu will call every savevm_state.handlers->save_live_complete_precopy callback + in "qemu_savevm_state_complete_precopy_iterable", and "vfio" handler will always behind "ram". + so here is question, my own vfio device will only be halted after "vfio" handler enter + save_live_complete_precopy, and last system memory dirty bitmap sync will come with "ram"'s + save_live_complete_precopy, there will be some system dirty between this period, should we add one more + system dirty bitmap sync after "vfio"'s save_live_complete_precopy + +second question: +- notice that qemu will clean up migration and call every savevm_state.handlers->save_cleanup call back, and + in this function, qemu will only call vfio listener's log_global_stop call back when vm_is_running + but for my vfio device, state will be paused(postmigrate) when enter here, so there is no chance for qemu + to relese some resource create by my device kernel mode driver, where should i put the logic about "stop + migration resource" anyway + +Thanks ^_^ +Steps to reproduce: +1. +2. +3. +Additional information: + -- cgit 1.4.1