summaryrefslogtreecommitdiff
path: root/exec.c
diff options
context:
space:
mode:
authorGonglei <arei.gonglei@huawei.com>2016-02-22 16:34:55 +0800
committerPaolo Bonzini <pbonzini@redhat.com>2016-02-25 16:11:26 +0100
commit58eaa2174e99d9a05172d03fd2799ab8fd9e6f60 (patch)
treeed5148b0d4e23bb0ea74372a85ecc3ba6fb3262a /exec.c
parent96c33a4523ee1abe382ce4ff3e82b90ba78aa186 (diff)
downloadqemu-58eaa2174e99d9a05172d03fd2799ab8fd9e6f60.tar.gz
exec: store RAMBlock pointer into memory region
Each RAM memory region has a unique corresponding RAMBlock. In the current realization, the memory region only stored the ram_addr which means the offset of RAM address space, We need to qurey the global ram.list to find the ram block by ram_addr if we want to get the ram block, which is very expensive. Now, we store the RAMBlock pointer into memory region structure. So, if we know the mr, we can easily get the RAMBlock. Signed-off-by: Gonglei <arei.gonglei@huawei.com> Message-Id: <1456130097-4208-2-git-send-email-arei.gonglei@huawei.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'exec.c')
-rw-r--r--exec.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/exec.c b/exec.c
index 1f2450002b..4c0114a1a1 100644
--- a/exec.c
+++ b/exec.c
@@ -1717,6 +1717,8 @@ ram_addr_t qemu_ram_alloc_internal(ram_addr_t size, ram_addr_t max_size,
error_propagate(errp, local_err);
return -1;
}
+
+ mr->ram_block = new_block;
return addr;
}