Is there any chance between 7.1 and 7.2 ‘something’ happened to make it so that Qemu ‘cares more’ about e.g. when memory regions are added/removed?
I seem to get an abort because a memory region has not been completely setup in 7.2 (while it is being flattened actually) - In 7.1 that never seemed to happen….? (Putting it all async work seems ‘excessive’ but maybe it’s needed now?) Cheers Mark On 28/12/2022, 14:04, "Philippe Mathieu-Daudé" <phi...@linaro.org> wrote: WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. When requesting the flatview output with 'info mtree -f', the MemoryRegion priority is irrelevant and noise. Remove it. Signed-off-by: Philippe Mathieu-Daudé <phi...@linaro.org> --- softmmu/memory.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/softmmu/memory.c b/softmmu/memory.c index e05332d07f..89713dd5ce 100644 --- a/softmmu/memory.c +++ b/softmmu/memory.c @@ -3330,22 +3330,20 @@ static void mtree_print_flatview(gpointer key, gpointer value, mr = range->mr; if (range->offset_in_region) { qemu_printf(MTREE_INDENT TARGET_FMT_plx "-" TARGET_FMT_plx - " (prio %d, %s%s): %s @" TARGET_FMT_plx, + " (%s%s): %s @" TARGET_FMT_plx, int128_get64(range->addr.start), int128_get64(range->addr.start) + MR_SIZE(range->addr.size), - mr->priority, range->nonvolatile ? "nv-" : "", range->readonly ? "rom" : memory_region_type(mr), memory_region_name(mr), range->offset_in_region); } else { qemu_printf(MTREE_INDENT TARGET_FMT_plx "-" TARGET_FMT_plx - " (prio %d, %s%s): %s", + " (%s%s): %s", int128_get64(range->addr.start), int128_get64(range->addr.start) + MR_SIZE(range->addr.size), - mr->priority, range->nonvolatile ? "nv-" : "", range->readonly ? "rom" : memory_region_type(mr), memory_region_name(mr)); -- 2.38.1