On 9/26/23 10:28, Maxim Levitsky wrote:
trace_kvm_exit is good example, where despite all of the information that is captured
by KVM, it's borderline worthless for CPUID and MSR exits because their interesting
information is held in registers and not captured in the VMCS or VMCB.
There are some on BTF type info issues that I've encountered, but I suspect that's
as much a PEBKAC problem as anything.
While eBPF has its use cases, none of the extra tracepoints were added solely because of
the monitoring tool and I do understand that tracepoints are a limited resource.
Each added tracepoint/info was added only when it was also found to be useful for regular
kvm tracing.
I am not sure about _all_ of them, but I agree with both of you.
On one hand, it would be pretty cool to have eBPF access to registers.
On the other hand, the specific info you're adding is generic and I
think there are only a couple exceptions where I am not sure it belongs
in the generic KVM tracepoints.
Paolo
