On 24.08.22 21:55, Peter Maydell wrote: > On Wed, 24 Aug 2022 at 17:43, David Hildenbrand <da...@redhat.com> wrote: >> One idea is doing another pass over the list at the end (after possible >> merging of sections) and making sure everything is page-aligned. >> >> Another idea is specifying somehow that that memory region should simply >> not be dumped ... >> >> >> But I do wonder why the ram memory region that's mapped into the guest >> physical address space has such a weird alignment/size ... > > Lumps of memory can be any size you like and anywhere in > memory you like. Sometimes we are modelling real hardware > that has done something like that. Sometimes it's just > a convenient way to model a device. Generic code in > QEMU does need to cope with this...
But we are talking about system RAM here. And judging by the fact that this is the first time dump.c blows up like this, this doesn't seem to very common, no? -- Thanks, David / dhildenb
