On 23/05/22 18:54, Andi Kleen wrote: > > On 5/17/2022 6:10 AM, Adrian Hunter wrote: >> Add an option to indicate that guest code can be found in the hypervisor >> process > > Sorry for harping on this, but is it correct that this assumes that the code is still at the original location at decode time? No, at decode time, the code is found in the hypervisor dso. > > If yes we need some warnings for this, something like: > > This only works when the code is still available in the riginal memory location at decode time. This is typically the case for kernel code (unless modules are unloaded). In this scenario, the VM does not have a kernel. Note, there is an existing method to trace a guest kernel as described here: https://www.man7.org/linux/man-pages/man1/perf-intel-pt.1.html#TRACING_VIRTUAL_MACHINES For user programs it only works as long as there is no memory pressure which might cause the memory to be reused. In this scenario, there are also no user programs in the VM, only functions from the hypervisor. For dynamically generated (JITed) code it might be rather unreliable unless the hypervisor is SIGSTOPed during decoding. >
