summaryrefslogtreecommitdiff
path: root/include
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 /include
parent96c33a4523ee1abe382ce4ff3e82b90ba78aa186 (diff)
downloadqemu-58eaa2174e99d9a05172d03fd2799ab8fd9e6f60.tar.gz
qemu-58eaa2174e99d9a05172d03fd2799ab8fd9e6f60.tar.bz2
qemu-58eaa2174e99d9a05172d03fd2799ab8fd9e6f60.zip
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 'include')
-rw-r--r--include/exec/memory.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/include/exec/memory.h b/include/exec/memory.h
index c92734ae2b..683be46cd0 100644
--- a/include/exec/memory.h
+++ b/include/exec/memory.h
@@ -34,6 +34,7 @@
#include "qapi/error.h"
#include "qom/object.h"
#include "qemu/rcu.h"
+#include "qemu/typedefs.h"
#define MAX_PHYS_ADDR_SPACE_BITS 62
#define MAX_PHYS_ADDR (((hwaddr)1 << MAX_PHYS_ADDR_SPACE_BITS) - 1)
@@ -172,6 +173,7 @@ struct MemoryRegion {
bool global_locking;
uint8_t dirty_log_mask;
ram_addr_t ram_addr;
+ RAMBlock *ram_block;
Object *owner;
const MemoryRegionIOMMUOps *iommu_ops;