diff options
| author | Zhang Chen | 2019-03-29 23:29:51 +0100 |
|---|---|---|
| committer | Dr. David Alan Gilbert | 2019-04-05 16:29:48 +0200 |
| commit | c6e5bafb6ff330e972eae7b823321143ab3e29e2 (patch) | |
| tree | 0a1fc0cb27d6123a8bdb7cf76dab2b58a9acf8a7 /python | |
| parent | Merge remote-tracking branch 'remotes/palmer/tags/riscv-for-master-4.0-rc3-v2... (diff) | |
| download | qemu-c6e5bafb6ff330e972eae7b823321143ab3e29e2.tar.gz qemu-c6e5bafb6ff330e972eae7b823321143ab3e29e2.tar.xz qemu-c6e5bafb6ff330e972eae7b823321143ab3e29e2.zip | |
migration/ram.c: Fix codes conflict about bitmap_mutex
I found upstream codes conflict with COLO and lead to crash,
and I located to this patch:
commit 386a907b37a9321bc5d699bc37104d6ffba1b34d
Author: Wei Wang <wei.w.wang@intel.com>
Date: Tue Dec 11 16:24:49 2018 +0800
migration: use bitmap_mutex in migration_bitmap_clear_dirty
My colleague Wei's patch add bitmap_mutex in migration_bitmap_clear_dirty,
but COLO didn't initialize the bitmap_mutex. So we always get an error
when COLO start up. like that:
qemu-system-x86_64: util/qemu-thread-posix.c:64: qemu_mutex_lock_impl: Assertion `mutex->initialized' failed.
This patch add the bitmap_mutex initialize and destroy in COLO
lifecycle.
Signed-off-by: Zhang Chen <chen.zhang@intel.com>
Message-Id: <20190329222951.28945-1-chen.zhang@intel.com>
Reviewed-by: Wei Wang <wei.w.wang@intel.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Diffstat (limited to 'python')
0 files changed, 0 insertions, 0 deletions