docs/devel/memory.rst

10 - memory controllers that can dynamically reroute physical memory regions
17 - setting up ioeventfd regions for kvm
20 (leaves) are RAM and MMIO regions, while other nodes represent
21 buses, memory controllers, and memory regions that have been rerouted.
27 Types of regions
30 There are multiple types of memory regions (all represented by a single C type
58 - container: a container simply includes other memory regions, each at
59   a different offset.  Containers are useful for grouping several regions
64   useful to have overlapping regions; for example a memory controller that
71   split apart into discontiguous regions. Examples of uses are memory
137 Regions are assigned names by the constructor.  For most regions these are
138 only used for debugging purposes, but RAM regions also use the name to identify
171 destroy memory regions dynamically during a device's lifetime, and only
190 therefore also okay to create or destroy alias and container regions
200 For regions that "have no owner" (NULL is passed at creation time), the
203 on regions that have no owner, unless they are aliases or containers.
206 Overlapping regions and priority
208 Usually, regions may not overlap each other; a memory address decodes into
209 exactly one target.  In some cases it is useful to allow regions to overlap,
210 and sometimes to control which of an overlapping regions is visible to the
213 specifies a priority that allows the core to decide which of two regions at
241 The regions that will be seen within this address range then are::
256 regions are only compared when they are both children of the same container.
259 its child regions without any side effects on other parts of the system.
345 MMIO regions are provided with ->read() and ->write() callbacks,