From 2d40178a33293603a06fdf3c0fd9988322bc5fda Mon Sep 17 00:00:00 2001 From: Paolo Bonzini Date: Mon, 6 May 2013 18:23:38 +0200 Subject: docs: mention AddressSpaces in docs/memory.txt Reported-by: David Gibson Signed-off-by: Paolo Bonzini Signed-off-by: Michael Tokarev --- docs/memory.txt | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'docs') diff --git a/docs/memory.txt b/docs/memory.txt index 5bbee8e85d..feb9fe90d7 100644 --- a/docs/memory.txt +++ b/docs/memory.txt @@ -15,10 +15,13 @@ The memory model provides support for - setting up coalesced memory for kvm - setting up ioeventfd regions for kvm -Memory is modelled as a tree (really acyclic graph) of MemoryRegion objects. -The root of the tree is memory as seen from the CPU's viewpoint (the system -bus). Nodes in the tree represent other buses, memory controllers, and -memory regions that have been rerouted. Leaves are RAM and MMIO regions. +Memory is modelled as an acyclic graph of MemoryRegion objects. Sinks +(leaves) are RAM and MMIO regions, while other nodes represent +buses, memory controllers, and memory regions that have been rerouted. + +In addition to MemoryRegion objects, the memory API provides AddressSpace +objects for every root and possibly for intermediate MemoryRegions too. +These represent memory as seen from the CPU or a device's viewpoint. Types of regions ---------------- -- cgit v1.2.1