At the moment may_overlap flag of MemoryRegion structure is used inconsistently, and ignored by the address range assignment process. In fact may_overlap flag can be fully substituted with priority of the MemoryRegion structure. Also usage of MemoryRegion priorities is a bit confusing. Exisiting priorities can take values 0,1,2 or even 1000.
This patch removes these drawbacks and introduces a predefined set of priorities for MemoryRegion. This code does not affect the exisiting memory topology build process, so does not cause any issues related to change of regions visibility. Alexey Korolev (3): Replacing memory_region_add_subregion_overlap Remove may_overlap flag from MemoryRegion structure Docs update: Overlapping memory regions and priority docs/memory.txt | 14 ++++++------ hw/armv7m_nvic.c | 4 ++-- hw/cirrus_vga.c | 15 +++++++------ hw/kvm/pci-assign.c | 7 +++--- hw/kvmvapic.c | 3 ++- hw/lpc_ich9.c | 7 +++--- hw/onenand.c | 7 +++--- hw/pam.c | 4 ++-- hw/pc.c | 6 ++---- hw/pc_sysfw.c | 14 ++++++------ hw/pci/pci.c | 4 ++-- hw/pci/pci_bridge.c | 3 ++- hw/piix_pci.c | 9 ++++---- hw/q35.c | 5 +++-- hw/sysbus.c | 7 ------ hw/sysbus.h | 2 -- hw/vga-isa.c | 7 +++--- hw/vga.c | 12 +++++------ hw/xen_pt_msi.c | 6 +++--- include/exec/memory.h | 42 +++++++++++++++++------------------- memory.c | 57 +++++++++++++++++++------------------------------ 21 files changed, 106 insertions(+), 129 deletions(-) -- 1.7.9.5
