docs/devel/memory.rst

58 - container: a container simply includes other memory regions, each at
63   A container's subregions are usually non-overlapping.  In some cases it is
68   You initialize a pure container with memory_region_init().
88 It is valid to add subregions to a region which is not a pure container
90 will act like a container, except that any addresses within the container's
92 container itself (ie by its MMIO callbacks or RAM backing). However
93 it is generally possible to achieve the same effect with a pure container
153 container with memory_region_add_subregion(), and removed using
189 object_unparent at any time for an alias or a container region.  It is
190 therefore also okay to create or destroy alias and container regions
212 allows the region to overlap any other region in the same container, and
220 If the higher priority region in an overlap is a container or alias, then
227 For example, suppose we have a container A of size 0x8000 with two subregions
228 B and C. B is a container mapped at 0x2000, size 0x4000, priority 2; C is
249 If B had provided its own MMIO operations (ie it was not a pure container)
255 Priority values are local to a container, because the priorities of two
256 regions are only compared when they are both children of the same container.
257 This means that the device in charge of the container (typically modelling
277   - if the subregion is a container, the same algorithm is used within the
281   - if a recursive search within a container or alias subregion does not
282     find a match (because of a "hole" in the container's coverage of its
283     address range), then if this is a container with its own MMIO or RAM
284     backing the search terminates, returning the container itself. Otherwise
295   system_memory: container@0-2^48-1
308    +--- vga-area: container@0xa0000-0xbffff