Hi, On 2018-03-23 11:03, Khalid Elmously wrote: > Starting from 4.13.0-38 the ubuntu kernel backport a kvm instrumentation > change introduced in 4.15 which affects the prototype of the kvm_mmio event. > > Signed-off-by: Khalid Elmously <khalid.elmou...@canonical.com> > --- > instrumentation/events/lttng-module/kvm.h | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/instrumentation/events/lttng-module/kvm.h > b/instrumentation/events/lttng-module/kvm.h > index 8f9a132..aba6f93 100644 > --- a/instrumentation/events/lttng-module/kvm.h > +++ b/instrumentation/events/lttng-module/kvm.h > @@ -92,6 +92,7 @@ LTTNG_TRACEPOINT_EVENT(kvm_ack_irq, > || LTTNG_KERNEL_RANGE(4,1,50, 4,2,0) \ > || LTTNG_KERNEL_RANGE(3,16,52, 3,17,0) \ > || LTTNG_KERNEL_RANGE(3,2,97, 3,3,0) \ > + || LTTNG_UBUNTU_KERNEL_RANGE(4,13,16,38, 4,14,255,255) \
I think the correct range should be (4,13,16,38, 4,14,0,0), if some kernels in the 4.14 branch are also affected another specific range macro should be added. > || LTTNG_DEBIAN_KERNEL_RANGE(4,9,65,0,3,0, 4,10,0,0,0,0) \ > || LTTNG_FEDORA_KERNEL_RANGE(4,14,13,300, 4,15,0,0)) > > And thanks for the patch! Michael _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
