Patchwork docs: mention AddressSpaces in docs/memory.txt

login
register
mail settings
Submitter Paolo Bonzini
Date May 6, 2013, 4:23 p.m.
Message ID <1367857418-14832-1-git-send-email-pbonzini@redhat.com>
Download mbox | patch
Permalink /patch/241720/
State New
Headers show

Comments

Paolo Bonzini - May 6, 2013, 4:23 p.m.
Reported-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
 docs/memory.txt | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)
Michael Tokarev - May 8, 2013, 7:22 a.m.
06.05.2013 20:23, Paolo Bonzini wrote:
> Reported-by: David Gibson <david@gibson.dropbear.id.au>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>  docs/memory.txt | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)

Thanks,  applied to the trivial patches tree.

/mjt

Patch

diff --git a/docs/memory.txt b/docs/memory.txt
index 5bbee8e..feb9fe9 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
 ----------------