[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEr6+EA-7H4tfpUhZqwLJA=nT+1NgXjwcKYuiqMrrDuC_Bj4hA@mail.gmail.com>
Date: Fri, 8 Apr 2022 22:21:18 +0800
From: Jeff Xie <xiehuan09@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: mingo@...hat.com, Masami Hiramatsu <mhiramat@...nel.org>,
Tom Zanussi <zanussi@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] tracing: make tp_printk work on syscall tracepoints
Hi,
Anyone have any suggestions for this patch series? ;-)
On Wed, Mar 30, 2022 at 12:39 AM Jeff Xie <xiehuan09@...il.com> 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
Powered by blists - more mailing lists