summary refs log tree commit diff stats
path: root/gitlab/issues/target_missing/host_missing/accel_missing/2480.toml
diff options
context:
space:
mode:
Diffstat (limited to 'gitlab/issues/target_missing/host_missing/accel_missing/2480.toml')
-rw-r--r--gitlab/issues/target_missing/host_missing/accel_missing/2480.toml37
1 files changed, 0 insertions, 37 deletions
diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/2480.toml b/gitlab/issues/target_missing/host_missing/accel_missing/2480.toml
deleted file mode 100644
index 65369e32..00000000
--- a/gitlab/issues/target_missing/host_missing/accel_missing/2480.toml
+++ /dev/null
@@ -1,37 +0,0 @@
-id = 2480
-title = "Two questions about VFIO device live migration"
-state = "closed"
-created_at = "2024-08-05T03:17:23.768Z"
-closed_at = "2025-03-10T21:32:03.771Z"
-labels = ["VFIO"]
-url = "https://gitlab.com/qemu-project/qemu/-/issues/2480"
-host-os = "Linux 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux"
-host-arch = "x86_64"
-qemu-version = "build qemu by myself with stable-6.0 branch"
-guest-os = "Linux"
-guest-arch = "x86_64"
-description = """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 ^_^"""
-reproduce = """1.
-2.
-3."""
-additional = """"""