linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <20220329163931.710555-1-xiehuan09@gmail.com> (raw)

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


             reply	other threads:[~2022-03-29 16:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 16:39 Jeff Xie [this message]
2022-03-29 16:39 ` [PATCH 1/3] tracing: make tracepoint_iter_lock public Jeff Xie
2022-03-29 16:39 ` [PATCH 2/3] tracing: make tracepoint_printk_key public Jeff Xie
2022-03-29 16:39 ` [PATCH 3/3] tracing: make tp_printk work on syscall tracepoints Jeff Xie
2022-04-08 21:18   ` Steven Rostedt
2022-04-09  2:17     ` Jeff Xie
2022-04-08 14:21 ` [PATCH 0/3] " Jeff Xie
2022-04-08 21:03   ` Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220329163931.710555-1-xiehuan09@gmail.com \
    --to=xiehuan09@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=zanussi@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).