| 1 | * Workflow for updating patches from newer kernel: |
| 2 | |
| 3 | Diff mainline/ and lttng-module/ directories. |
| 4 | |
| 5 | Pull the new headers from mainline kernel to mainline/. |
| 6 | Copy them into lttng-modules. |
| 7 | Apply diff. Fix conflicts. |
| 8 | |
| 9 | |
| 10 | * Workflow to add new Tracepoint instrumentation to newer kernel, |
| 11 | and add support for it into LTTng: |
| 12 | |
| 13 | a) instrument the kernel with new trace events headers. If you want that |
| 14 | instrumentation distributed, you will have to push those changes into |
| 15 | the upstream Linux kernel first, |
| 16 | b) copy those headers into lttng mainline/ directory, |
| 17 | c) look at a diff from other headers between mainline/ and |
| 18 | lttng/, and use that as a recipe to create a new lttng/ |
| 19 | header from the mainline/ header, |
| 20 | d) create a new file in probes/ for the new trace event header you added, |
| 21 | e) add it to probes/Makefile, |
| 22 | f) build, make modules_install, |
| 23 | g) don't forget to load that new module too. |
| 24 | |
| 25 | Currently, LTTng policy is to only accept headers derived from trace |
| 26 | event headers accepted into the Linux kernel upstream for tracepoints |
| 27 | related to upstream kernel instrumentation. |