Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate hypervisor/guest/vm behaviour. #350

Open
cvonelm opened this issue Nov 7, 2024 · 0 comments
Open

Investigate hypervisor/guest/vm behaviour. #350

cvonelm opened this issue Nov 7, 2024 · 0 comments

Comments

@cvonelm
Copy link
Member

cvonelm commented Nov 7, 2024

perf has a lot of options to control how it interacts with guest VMs below it and hypervisors above it.

Currently, lo2s is oblivious to the fact that virtualization exists.

It would be nice to know:

  • What already works right now without any manual intervention
  • What we could gain from making lo2s vm-aware
  • What things are possible and what are almost certainly impossible (for example, I think that sample resolution for IPs in the hypervisor is going to be pretty hard, because we have to look up binaries in the hypervisor)

Something to keep in mind, and which started of this whole discussion is the existence of

PERF_CONTEXT_GUEST_{KERNEL, USER} and PERF_CONTEXT_HV callstack markers, which show you where in the callstack the guest/hypervisor begins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant