Separate thread for VM migration
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 12 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | Support for vm_stop from the migration threadcpus.c | +2 | 2 replies | |
| 2/5 | MRU ram block listcpu-all.h exec.c | +14 | 0 replies | |
| 3/5 | Migration thread mutexarch_init.c cpu-all.h exec.c +1 more | +49 | 3 replies | |
| 4/5 | Separate migration dirty bitmaparch_init.c cpu-all.h exec.c | +102 | 0 replies | |
| 5/5 | Separate migration threadbuffered_file.c migration.c migration.h +2 more | +124 | 5 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/5] Separate thread for VM migration
Following patch series deals with VCPU and iothread starvation during the migration of a guest. Currently the iothread is responsible for performing the guest migration. It holds qemu_mutex during the migration and doesn't allow VCPU to enter the qemu mode and delays its return to the guest. The guest migration, executed as an iohandler also delays the execution of other iohandlers. In the following patch series,
The migration has been moved to a separate thread to reduce the qemu_mutex contention and iohandler starvation.
Umesh Deshpande (5):
vm_stop from non-io threads
MRU ram block list
migration thread mutex
separate migration bitmap
separate migration thread
arch_init.c | 38 +++++++++++++---- buffered_file.c | 76 ++++++++++++++++++--------------- cpu-all.h | 42 ++++++++++++++++++ cpus.c | 4 +- exec.c | 97 ++++++++++++++++++++++++++++++++++++++++-- migration.c | 117 ++++++++++++++++++++++++++++++++------------------- migration.h | 9 ++++ qemu-common.h | 2 + qemu-thread-posix.c | 10 ++++ qemu-thread.h | 1 + 10 files changed, 302 insertions(+), 94 deletions(-)
Signature · 1 line
1.7.4.1