From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 8/8] tracing: Update modules to persistent instances when loaded
Date: Thu, 6 Feb 2025 19:01:24 +0900 [thread overview]
Message-ID: <20250206190124.1518c3bf070e862da7993d9e@kernel.org> (raw)
In-Reply-To: <20250205225104.264333506@goodmis.org>
On Wed, 05 Feb 2025 17:50:39 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> From: Steven Rostedt <rostedt@goodmis.org>
>
> When a module is loaded and a persistent buffer is actively tracing, add
> it to the list of modules in the persistent memory.
>
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
> kernel/trace/trace.c | 25 +++++++++++++++++++++++
> kernel/trace/trace.h | 2 ++
> kernel/trace/trace_events.c | 40 ++++++++++++++++++++++++++-----------
> 3 files changed, 55 insertions(+), 12 deletions(-)
>
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index 7b4027804cd4..443f2bc5b856 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -10088,6 +10088,30 @@ static void trace_module_remove_evals(struct module *mod)
> static inline void trace_module_remove_evals(struct module *mod) { }
> #endif /* CONFIG_TRACE_EVAL_MAP_FILE */
>
> +static bool trace_array_active(struct trace_array *tr)
> +{
> + if (tr->current_trace != &nop_trace)
> + return true;
> +
> + /* 0 is no events, 1 is all disabled */
> + return trace_events_enabled(tr, NULL) > 1;
> +}
> +
> +static void trace_module_record(struct module *mod)
> +{
> + struct trace_array *tr;
> +
> + list_for_each_entry(tr, &ftrace_trace_arrays, list) {
> + /* Update any persistent trace array that has already been started */
> + if ((tr->flags & (TRACE_ARRAY_FL_BOOT | TRACE_ARRAY_FL_LAST_BOOT)) ==
> + TRACE_ARRAY_FL_BOOT) {
> + /* Only update if the trace array is active */
> + if (trace_array_active(tr))
Do we really need this check? It seems that we can just save_mod() if the
above condition is true.
> + save_mod(mod, tr);
> + }
> + }
> +}
> +
> static int trace_module_notify(struct notifier_block *self,
> unsigned long val, void *data)
> {
> @@ -10096,6 +10120,7 @@ static int trace_module_notify(struct notifier_block *self,
> switch (val) {
> case MODULE_STATE_COMING:
> trace_module_add_evals(mod);
> + trace_module_record(mod);
> break;
> case MODULE_STATE_GOING:
> trace_module_remove_evals(mod);
Don't we need to remove the module entry when a module is removed?
(everytime we remove a module, trace data is cleared?)
Thank you,
> diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
> index 3a020fb82a34..90493220c362 100644
> --- a/kernel/trace/trace.h
> +++ b/kernel/trace/trace.h
> @@ -786,6 +786,8 @@ extern void trace_find_cmdline(int pid, char comm[]);
> extern int trace_find_tgid(int pid);
> extern void trace_event_follow_fork(struct trace_array *tr, bool enable);
>
> +extern int trace_events_enabled(struct trace_array *tr, const char *system);
> +
> #ifdef CONFIG_DYNAMIC_FTRACE
> extern unsigned long ftrace_update_tot_cnt;
> extern unsigned long ftrace_number_of_pages;
> diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
> index 4cb275316e51..107767afe0ab 100644
> --- a/kernel/trace/trace_events.c
> +++ b/kernel/trace/trace_events.c
> @@ -1811,28 +1811,28 @@ event_enable_write(struct file *filp, const char __user *ubuf, size_t cnt,
> return cnt;
> }
>
> -static ssize_t
> -system_enable_read(struct file *filp, char __user *ubuf, size_t cnt,
> - loff_t *ppos)
> +/*
> + * Returns:
> + * 0 : no events exist?
> + * 1 : all events are disabled
> + * 2 : all events are enabled
> + * 3 : some events are enabled and some are enabled
> + */
> +int trace_events_enabled(struct trace_array *tr, const char *system)
> {
> - const char set_to_char[4] = { '?', '0', '1', 'X' };
> - struct trace_subsystem_dir *dir = filp->private_data;
> - struct event_subsystem *system = dir->subsystem;
> struct trace_event_call *call;
> struct trace_event_file *file;
> - struct trace_array *tr = dir->tr;
> - char buf[2];
> int set = 0;
> - int ret;
>
> - mutex_lock(&event_mutex);
> + guard(mutex)(&event_mutex);
> +
> list_for_each_entry(file, &tr->events, list) {
> call = file->event_call;
> if ((call->flags & TRACE_EVENT_FL_IGNORE_ENABLE) ||
> !trace_event_name(call) || !call->class || !call->class->reg)
> continue;
>
> - if (system && strcmp(call->class->system, system->name) != 0)
> + if (system && strcmp(call->class->system, system) != 0)
> continue;
>
> /*
> @@ -1848,7 +1848,23 @@ system_enable_read(struct file *filp, char __user *ubuf, size_t cnt,
> if (set == 3)
> break;
> }
> - mutex_unlock(&event_mutex);
> +
> + return set;
> +}
> +
> +static ssize_t
> +system_enable_read(struct file *filp, char __user *ubuf, size_t cnt,
> + loff_t *ppos)
> +{
> + const char set_to_char[4] = { '?', '0', '1', 'X' };
> + struct trace_subsystem_dir *dir = filp->private_data;
> + struct event_subsystem *system = dir->subsystem;
> + struct trace_array *tr = dir->tr;
> + char buf[2];
> + int set;
> + int ret;
> +
> + set = trace_events_enabled(tr, system ? system->name : NULL);
>
> buf[0] = set_to_char[set];
> buf[1] = '\n';
> --
> 2.45.2
>
>
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2025-02-06 10:01 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 22:50 [PATCH 0/8] ring-buffer/tracing: Save module information in persistent memory Steven Rostedt
2025-02-05 22:50 ` [PATCH 1/8] ring-buffer: Use kaslr address instead of text delta Steven Rostedt
2025-02-06 0:32 ` Masami Hiramatsu
2025-02-05 22:50 ` [PATCH 2/8] ring-buffer: Add buffer meta data for persistent ring buffer Steven Rostedt
2025-02-06 5:10 ` Masami Hiramatsu
2025-02-06 15:19 ` Steven Rostedt
2025-02-05 22:50 ` [PATCH 3/8] ring-buffer: Add ring_buffer_meta_scratch() Steven Rostedt
2025-02-06 5:13 ` Masami Hiramatsu
2025-02-05 22:50 ` [PATCH 4/8] tracing: Have persistent trace instances save KASLR offset Steven Rostedt
2025-02-06 5:22 ` Masami Hiramatsu
2025-02-06 15:24 ` Steven Rostedt
2025-02-07 0:58 ` Masami Hiramatsu
2025-02-07 1:03 ` Steven Rostedt
2025-02-07 2:15 ` Masami Hiramatsu
2025-02-05 22:50 ` [PATCH 5/8] module: Add module_for_each_mod() function Steven Rostedt
2025-02-06 5:28 ` Masami Hiramatsu
2025-02-06 15:27 ` Steven Rostedt
2025-02-10 13:04 ` Petr Pavlu
2025-02-10 14:08 ` Sebastian Andrzej Siewior
2025-02-14 22:30 ` Steven Rostedt
2025-02-18 21:21 ` Luis Chamberlain
2025-02-18 21:29 ` Steven Rostedt
2025-02-19 0:24 ` Steven Rostedt
2025-02-19 16:02 ` Luis Chamberlain
2025-02-05 22:50 ` [PATCH 6/8] tracing: Have persistent trace instances save module addresses Steven Rostedt
2025-02-06 8:26 ` Masami Hiramatsu
2025-02-06 15:29 ` Steven Rostedt
2025-02-06 16:53 ` Masami Hiramatsu
2025-02-05 22:50 ` [PATCH 7/8] tracing: Show module names and addresses of last boot Steven Rostedt
2025-02-07 1:51 ` Masami Hiramatsu
2025-02-07 2:02 ` Steven Rostedt
2025-02-07 2:25 ` Masami Hiramatsu
2025-02-05 22:50 ` [PATCH 8/8] tracing: Update modules to persistent instances when loaded Steven Rostedt
2025-02-06 10:01 ` Masami Hiramatsu [this message]
2025-02-06 15:36 ` Steven Rostedt
2025-02-06 16:53 ` Masami Hiramatsu
2025-02-06 16:58 ` [PATCH 1/3] tracing: Skip update_last_data() if it is already updated Masami Hiramatsu (Google)
2025-02-06 16:58 ` [PATCH 2/3] tracing: Remove checking the activity when module map is updating Masami Hiramatsu (Google)
2025-03-07 15:21 ` Steven Rostedt
2025-03-11 0:40 ` Masami Hiramatsu
2025-02-06 16:59 ` [PATCH 3/3] tracing: Show last module text symbols in the stacktrace Masami Hiramatsu (Google)
2025-02-06 17:46 ` Steven Rostedt
2025-02-07 1:50 ` Masami Hiramatsu
2025-02-06 17:18 ` [PATCH 8/8] tracing: Update modules to persistent instances when loaded Steven Rostedt
2025-02-07 0:47 ` Masami Hiramatsu
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=20250206190124.1518c3bf070e862da7993d9e@kernel.org \
--to=mhiramat@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.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