OpenE2K/qemu-e2k
13
4
Fork 0
Code Issues 4 Pull Requests Projects 2 Releases Activity

docs: mention AddressSpaces in docs/memory.txt

Browse Source 
Reported-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
This commit is contained in:
Paolo Bonzini 2013-05-06 18:23:38 +02:00 committed by Michael Tokarev
parent 59d8276293
commit 2d40178a33
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/memory.txt
View File

@ -15,10 +15,13 @@ The memory model provides support for
- setting up coalesced memory for kvm - setting up coalesced memory for kvm
- setting up ioeventfd regions for kvm - setting up ioeventfd regions for kvm
Memory is modelled as a tree (really acyclic graph) of MemoryRegion objects. Memory is modelled as an acyclic graph of MemoryRegion objects. Sinks
The root of the tree is memory as seen from the CPU's viewpoint (the system (leaves) are RAM and MMIO regions, while other nodes represent
bus). Nodes in the tree represent other buses, memory controllers, and buses, memory controllers, and memory regions that have been rerouted.
memory regions that have been rerouted. Leaves are RAM and MMIO regions.
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 Types of regions
---------------- ----------------