We usually backport tracepoint instrumentation updates to support newer kernels, but as Alexandre Montplaisir pointed out, there is a significant tracepoint API change introduced in kernel 3.15 that requires the new lttng-tracepoint.c adapter, and I would consider it far-fetched to backport it as a fix. This is why we chose not to support kernels 3.15+ in lttng-modules 2.4.
Therefore, upgrading to lttng-modules 2.5 would be the appropriate solution. Please keep in mind that this is not usually required. This is a rare situation where there has been a significant module API change in the Linux kernel that required implementing a new adapter to support the new kernel.
Hi,
We usually backport tracepoint instrumentation updates to support newer kernels, but as Alexandre Montplaisir pointed out, there is a significant tracepoint API change introduced in kernel 3.15 that requires the new lttng-tracepoint.c adapter, and I would consider it far-fetched to backport it as a fix. This is why we chose not to support kernels 3.15+ in lttng-modules 2.4.
Therefore, upgrading to lttng-modules 2.5 would be the appropriate solution. Please keep in mind that this is not usually required. This is a rare situation where there has been a significant module API change in the Linux kernel that required implementing a new adapter to support the new kernel.
Thanks,
Mathieu