On Tue, 16 Apr 2024 at 17:53, Don Porter <por...@cs.unc.edu> wrote: > There is still a lot I am learning about the code base, but it seems > that qemu_get_guest_memory_mapping() does most of what one would need. > It currently only returns the "leaves" of the page table tree in a list. > > What if I extend this function with an optional argument to either > 1) return the interior nodes of the page table in additional lists (and > then parse+print in the monitor code), or > 2) inline the monitor printing in the arch-specific hook, and pass a > flag to get_guest_memory_mapping() that turns on/off the statements that > pretty print the page tables? > > It looks like most CPUs implement this function as part of checkpointing.
As far as I can see only x86 implements the get_memory_mapping function, so once again somebody has added some bit of functionality that does a walk of the page tables that is x86 only and that shares no code with any of the other page table walking code :-( thanks -- PMM
