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 1/3] tracing: make tracepoint_iter_lock public
Date: Wed, 30 Mar 2022 00:39:29 +0800 [thread overview]
Message-ID: <20220329163931.710555-2-xiehuan09@gmail.com> (raw)
In-Reply-To: <20220329163931.710555-1-xiehuan09@gmail.com>
The syscall tracepoints need tracepoint_iter_lock for the tp_printk work.
Signed-off-by: Jeff Xie <xiehuan09@gmail.com>
---
kernel/trace/trace.c | 2 +-
kernel/trace/trace.h | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index eaf7d30ca6f1..867f00473f9f 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -2833,7 +2833,7 @@ trace_event_buffer_lock_reserve(struct trace_buffer **current_rb,
}
EXPORT_SYMBOL_GPL(trace_event_buffer_lock_reserve);
-static DEFINE_SPINLOCK(tracepoint_iter_lock);
+DEFINE_SPINLOCK(tracepoint_iter_lock);
static DEFINE_MUTEX(tracepoint_printk_mutex);
static void output_printk(struct trace_event_buffer *fbuffer)
diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
index 0f5e22238cd2..7ce345699ac2 100644
--- a/kernel/trace/trace.h
+++ b/kernel/trace/trace.h
@@ -1523,6 +1523,7 @@ static inline void *event_file_data(struct file *filp)
extern struct mutex event_mutex;
extern struct list_head ftrace_events;
+extern spinlock_t tracepoint_iter_lock;
extern const struct file_operations event_trigger_fops;
extern const struct file_operations event_hist_fops;
--
2.25.1
next prev parent reply other threads:[~2022-03-29 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 16:39 [PATCH 0/3] tracing: make tp_printk work on syscall tracepoints Jeff Xie
2022-03-29 16:39 ` Jeff Xie [this message]
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-2-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
all inboxes | Powered by JetHome®