summaryrefslogtreecommitdiff
path: root/Documentation/trace
diff options
context:
space:
mode:
authorJianlin Lv <iecedge@gmail.com>2022-11-02 19:02:36 +0300
committerSteven Rostedt (Google) <rostedt@goodmis.org>2023-02-18 22:34:36 +0300
commite7bb66f79a7b19a47b3eff745ea9f7ba1ae76032 (patch)
tree53d19c415d584471bf0686596a270cac22c2314f /Documentation/trace
parent2455f0e124d317dd08d337a7550a78a224d4ba41 (diff)
downloadlinux-e7bb66f79a7b19a47b3eff745ea9f7ba1ae76032.tar.xz
tracepoint: Allow livepatch module add trace event
In the case of keeping the system running, the preferred method for tracing the kernel is dynamic tracing (kprobe), but the drawback of this method is that events are lost, especially when tracing packages in the network stack. Livepatching provides a potential solution, which is to reimplement the function you want to replace and insert a static tracepoint. In such a way, custom stable static tracepoints can be expanded without rebooting the system. Link: https://lkml.kernel.org/r/20221102160236.11696-1-iecedge@gmail.com Signed-off-by: Jianlin Lv <iecedge@gmail.com> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Diffstat (limited to 'Documentation/trace')
0 files changed, 0 insertions, 0 deletions