From: Alex Williamson <alex.williamson@redhat.com>
Date: Wed, 14 Jul 2010 19:36:49 +0000 (-0600)
Subject: kvm: Don't walk memory_size == 0 slots in kvm_client_migration_log
X-Git-Tag: TizenStudio_2.0_p2.3.2~208^2~7271^2~1
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=70fedd76d9fe4900651f3360725fb511a19d03d5;p=sdk%2Femulator%2Fqemu.git

kvm: Don't walk memory_size == 0 slots in kvm_client_migration_log

If we've unregistered a memory area, we should avoid calling
qemu_get_ram_ptr() on the left over phys_offset cruft in the
slot array.  Now that we support removing ramblocks, the
phys_offset ram_addr_t can go away and cause a lookup fault
and abort.

Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
---

diff --git a/kvm-all.c b/kvm-all.c
index 7635f2f..736c516 100644
--- a/kvm-all.c
+++ b/kvm-all.c
@@ -274,6 +274,9 @@ static int kvm_set_migration_log(int enable)
     for (i = 0; i < ARRAY_SIZE(s->slots); i++) {
         mem = &s->slots[i];
 
+        if (!mem->memory_size) {
+            continue;
+        }
         if (!!(mem->flags & KVM_MEM_LOG_DIRTY_PAGES) == enable) {
             continue;
         }