summaryrefslogtreecommitdiff
path: root/Makefile.target
diff options
context:
space:
mode:
authorAvi Kivity <avi@redhat.com>2011-07-26 14:26:01 +0300
committerAnthony Liguori <aliguori@us.ibm.com>2011-07-29 08:25:42 -0500
commit093bc2cd885e4e3420509a80a1b9e81848e4b8fe (patch)
treea75dc34dbddaeb5283025f182eb9a84022b1bfff /Makefile.target
parent9d3a4736cb86f0ad7904b223eccb165de8d4327b (diff)
downloadqemu-093bc2cd885e4e3420509a80a1b9e81848e4b8fe.tar.gz
qemu-093bc2cd885e4e3420509a80a1b9e81848e4b8fe.tar.bz2
qemu-093bc2cd885e4e3420509a80a1b9e81848e4b8fe.zip
Hierarchical memory region API
The memory API separates the attributes of a memory region (its size, how reads or writes are handled, dirty logging, and coalescing) from where it is mapped and whether it is enabled. This allows a device to configure a memory region once, then hand it off to its parent bus to map it according to the bus configuration. Hierarchical registration also allows a device to compose a region out of a number of sub-regions with different properties; for example some may be RAM while others may be MMIO. Reviewed-by: Anthony Liguori <aliguori@us.ibm.com> Signed-off-by: Avi Kivity <avi@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'Makefile.target')
-rw-r--r--Makefile.target1
1 files changed, 1 insertions, 0 deletions
diff --git a/Makefile.target b/Makefile.target
index cde509ba76..8884a56aa3 100644
--- a/Makefile.target
+++ b/Makefile.target
@@ -198,6 +198,7 @@ obj-$(CONFIG_REALLY_VIRTFS) += 9pfs/virtio-9p-device.o
obj-y += rwhandler.o
obj-$(CONFIG_KVM) += kvm.o kvm-all.o
obj-$(CONFIG_NO_KVM) += kvm-stub.o
+obj-y += memory.o
LIBS+=-lz
QEMU_CFLAGS += $(VNC_TLS_CFLAGS)