Currently the tp_printk option has no effect on syscall tracepoint.
When adding the kernel option parameter tp_printk, then:
echo 1 > /sys/kernel/debug/tracing/events/syscalls/enable
When running any application, no trace information is printed on the
terminal.
Now added printk for syscall tracepoints.
Jeff Xie (3):
tracing: make tracepoint_iter_lock public
tracing: make tracepoint_printk_key public
tracing: make tp_printk work on syscall tracepoints
kernel/trace/trace.c | 4 ++--
kernel/trace/trace.h | 2 ++
kernel/trace/trace_syscalls.c | 25 +++++++++++++++++++++++++
3 files changed, 29 insertions(+), 2 deletions(-)
--
2.25.1
Hi,
Anyone have any suggestions for this patch series? ;-)
On Wed, Mar 30, 2022 at 12:39 AM Jeff Xie <[email protected]> wrote:
>
> Currently the tp_printk option has no effect on syscall tracepoint.
> When adding the kernel option parameter tp_printk, then:
>
> echo 1 > /sys/kernel/debug/tracing/events/syscalls/enable
>
> When running any application, no trace information is printed on the
> terminal.
>
> Now added printk for syscall tracepoints.
>
> Jeff Xie (3):
> tracing: make tracepoint_iter_lock public
> tracing: make tracepoint_printk_key public
> tracing: make tp_printk work on syscall tracepoints
>
> kernel/trace/trace.c | 4 ++--
> kernel/trace/trace.h | 2 ++
> kernel/trace/trace_syscalls.c | 25 +++++++++++++++++++++++++
> 3 files changed, 29 insertions(+), 2 deletions(-)
>
> --
> 2.25.1
>
---
JeffXie
On Fri, 8 Apr 2022 22:21:18 +0800
Jeff Xie <[email protected]> wrote:
> Anyone have any suggestions for this patch series? ;-)
Thanks for the reminder. I'll look at them now.
-- Steve