On Wed, Dec 28, 2022 at 02:04:39PM +0100, Philippe Mathieu-Daudé wrote:
> When requesting the flatview output with 'info mtree -f',
> the MemoryRegion priority is irrelevant and noise. Remove it.
It is in many cases still helpful debugging information to me.
Maybe it's because it can cause mis-al
On 28/12/22 17:26, Mark Burton wrote:
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 flatt
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 seeme
When requesting the flatview output with 'info mtree -f',
the MemoryRegion priority is irrelevant and noise. Remove it.
Signed-off-by: Philippe Mathieu-Daudé
---
softmmu/memory.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/softmmu/memory.c b/softmmu/memory.c
index e
