linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Li Chen <me@linux.beauty>
Cc: linux-trace-kernel@vger.kernel.org,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH] ftrace: Use this_cpu_ptr() instead of per_cpu_ptr(smp_processor_id())
Date: Mon, 19 Aug 2024 11:23:01 -0400	[thread overview]
Message-ID: <20240819112301.7c178eff@gandalf.local.home> (raw)
In-Reply-To: <87y14t6ofi.wl-me@linux.beauty>

On Mon, 19 Aug 2024 14:01:53 +0800
Li Chen <me@linux.beauty> wrote:

> From: Li Chen <chenl311@chinatelecom.cn>
> 
> Use this_cpu_ptr() instead of open coding the equivalent in various
> ftrace functions.

Thanks.

This code was written (2009) before this_cpu_ptr() was introduced (2010).

-- Steve

> 
> Signed-off-by: Li Chen <chenl311@chinatelecom.cn>
> ---
>  kernel/trace/trace_functions.c | 10 +++-------
>  1 file changed, 3 insertions(+), 7 deletions(-)
> 
> diff --git a/kernel/trace/trace_functions.c b/kernel/trace/trace_functions.c
> index 3b0cea37e0297..65fed0bbc5c22 100644
> --- a/kernel/trace/trace_functions.c
> +++ b/kernel/trace/trace_functions.c
> @@ -184,7 +184,6 @@ function_trace_call(unsigned long ip, unsigned long parent_ip,
>  	struct trace_array_cpu *data;
>  	unsigned int trace_ctx;
>  	int bit;
> -	int cpu;
>  
>  	if (unlikely(!tr->function_enabled))
>  		return;
> @@ -195,8 +194,7 @@ function_trace_call(unsigned long ip, unsigned long parent_ip,
>  
>  	trace_ctx = tracing_gen_ctx();
>  
> -	cpu = smp_processor_id();
> -	data = per_cpu_ptr(tr->array_buffer.data, cpu);
> +	data = this_cpu_ptr(tr->array_buffer.data);
>  	if (!atomic_read(&data->disabled))
>  		trace_function(tr, ip, parent_ip, trace_ctx);
>  
> @@ -300,7 +298,6 @@ function_no_repeats_trace_call(unsigned long ip, unsigned long parent_ip,
>  	unsigned int trace_ctx;
>  	unsigned long flags;
>  	int bit;
> -	int cpu;
>  
>  	if (unlikely(!tr->function_enabled))
>  		return;
> @@ -309,8 +306,7 @@ function_no_repeats_trace_call(unsigned long ip, unsigned long parent_ip,
>  	if (bit < 0)
>  		return;
>  
> -	cpu = smp_processor_id();
> -	data = per_cpu_ptr(tr->array_buffer.data, cpu);
> +	data = this_cpu_ptr(tr->array_buffer.data);
>  	if (atomic_read(&data->disabled))
>  		goto out;
>  
> @@ -321,7 +317,7 @@ function_no_repeats_trace_call(unsigned long ip, unsigned long parent_ip,
>  	 * TODO: think about a solution that is better than just hoping to be
>  	 * lucky.
>  	 */
> -	last_info = per_cpu_ptr(tr->last_func_repeats, cpu);
> +	last_info = this_cpu_ptr(tr->last_func_repeats);
>  	if (is_repeat_check(tr, last_info, ip, parent_ip))
>  		goto out;
>  


      reply	other threads:[~2024-08-19 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19  6:01 [PATCH] ftrace: Use this_cpu_ptr() instead of per_cpu_ptr(smp_processor_id()) Li Chen
2024-08-19 15:23 ` Steven Rostedt [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=20240819112301.7c178eff@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=me@linux.beauty \
    --cc=mhiramat@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).