public inbox for linux-trace-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <zanussi@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	 Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH] tracing: Remove notrace from trace_event_raw_event_synth()
Date: Sun, 25 Jan 2026 13:24:25 -0600	[thread overview]
Message-ID: <8d8d91b883a8f0ed002bfec51f31f82ccbc8cd6a.camel@kernel.org> (raw)
In-Reply-To: <20260122204526.068a98c9@gandalf.local.home>

Hi Steve,

On Thu, 2026-01-22 at 20:45 -0500, Steven Rostedt wrote:
> From: Steven Rostedt <rostedt@goodmis.org>
> 
> When debugging the synthetic events, being able to function trace its
> functions is very useful (now that CONFIG_FUNCTION_SELF_TRACING is
> available). For some reason trace_event_raw_event_synth() was marked as
> "notrace", which was totally unnecessary as all of the tracing directory
> had function tracing disabled until the recent FUNCTION_SELF_TRACING was
> added.
> 
> Remove the notrace annotation from trace_event_raw_event_synth() as
> there's no reason to not trace it when tracing synthetic event functions.
> 
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

Acked-by: Tom Zanussi <zanussi@kernel.org>

Thanks,

Tom

> ---
>  kernel/trace/trace_events_synth.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/kernel/trace/trace_events_synth.c b/kernel/trace/trace_events_synth.c
> index 4554c458b78c..79a506fc2856 100644
> --- a/kernel/trace/trace_events_synth.c
> +++ b/kernel/trace/trace_events_synth.c
> @@ -493,9 +493,9 @@ static unsigned int trace_stack(struct synth_trace_event *entry,
>  	return len;
>  }
>  
> -static notrace void trace_event_raw_event_synth(void *__data,
> -						u64 *var_ref_vals,
> -						unsigned int *var_ref_idx)
> +static void trace_event_raw_event_synth(void *__data,
> +					u64 *var_ref_vals,
> +					unsigned int *var_ref_idx)
>  {
>  	unsigned int i, n_u64, val_idx, len, data_size = 0;
>  	struct trace_event_file *trace_file = __data;


      reply	other threads:[~2026-01-25 19:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23  1:45 [PATCH] tracing: Remove notrace from trace_event_raw_event_synth() Steven Rostedt
2026-01-25 19:24 ` Tom Zanussi [this message]

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=8d8d91b883a8f0ed002bfec51f31f82ccbc8cd6a.camel@kernel.org \
    --to=zanussi@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --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