docs/devel/memory.rst

15 - tracking RAM changes by the guest
30 There are multiple types of memory regions (all represented by a single C type
39 - MMIO: a range of guest memory that is implemented by host callbacks;
83   It claims I/O space that is not supposed to be handled by QEMU itself.
85   handled by the host kernel when KVM is enabled.  You initialize these
86   by passing a NULL callback parameter to memory_region_init_io().
91 region which are not claimed by any subregion are handled by the
92 container itself (ie by its MMIO callbacks or RAM backing). However
101 Where the memory region is backed by host memory (RAM, ROM and
137 Regions are assigned names by the constructor.  For most regions these are
145 A region is created by one of the memory_region_init*() functions and
148 the guest, or as long as the region is in use by a virtual CPU or another
169 You must not destroy a memory region as long as it may be in use by a
180   (for example by address_space_map)
222 region has left by not mapping subregions to that area of its address range.
250 then these would be used for any addresses in its range not handled by
278     subregion (after the address is adjusted by the subregion offset)
280     (after the address is adjusted by the subregion offset and alias offset)
329 can be removed by programming the memory controller; this is modelled by
335 by two 32K memory banks pointing at two sections of the framebuffer.
362   (in bytes) supported by the *implementation*; other access sizes will be
366   accesses; if false, unaligned accesses will be emulated by two aligned