[lttng-dev] Unexport of kvm_x86_ops vs tracer modules

2022-04-08 Thread Mathieu Desnoyers via lttng-dev
Hi Sean, Hi Paolo, I have a question regarding a unexport of kvm_x86_ops that made its way into 5.18-rc (commit dfc4e6ca04 ("KVM: x86: Unexport kvm_x86_ops"). This is in the context of tracing. Especially, LTTng implements probes for x86 kvm events, e.g. x86 kvm_exit. It receives a struct kvm_vcpu

Re: [lttng-dev] Unexport of kvm_x86_ops vs tracer modules

2022-04-08 Thread Paolo Bonzini via lttng-dev
On 4/8/22 17:36, Mathieu Desnoyers wrote: LTTng is an out of tree kernel module, which currently relies on the export. Indeed, arch/x86/kvm/x86.c exports a set of tracepoints to kernel modules, e.g.: EXPORT_TRACEPOINT_SYMBOL_GPL(kvm_entry) But any probe implementation hooking on that tracepoint

Re: [lttng-dev] Unexport of kvm_x86_ops vs tracer modules

2022-04-08 Thread Mathieu Desnoyers via lttng-dev
- On Apr 8, 2022, at 12:24 PM, Paolo Bonzini pbonz...@redhat.com wrote: > On 4/8/22 17:36, Mathieu Desnoyers wrote: >> LTTng is an out of tree kernel module, which currently relies on the export. >> Indeed, arch/x86/kvm/x86.c exports a set of tracepoints to kernel modules, >> e.g.: >> >> EXP