Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
From:   Jeff Xie <xiehuan09@gmail.com>
To:     rostedt@goodmis.org
Cc:     mingo@redhat.com, mhiramat@kernel.org, zanussi@kernel.org,
        linux-kernel@vger.kernel.org, Jeff Xie <xiehuan09@gmail.com>
Subject: [PATCH 0/3] tracing: make tp_printk work on syscall tracepoints
Date:   Wed, 30 Mar 2022 00:39:28 +0800
Message-Id: <20220329163931.710555-1-xiehuan09@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

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