Linux Trace Kernel
 help / color / mirror / Atom feed
From: Mukesh Ojha <quic_mojha@quicinc.com>
To: Douglas RAILLARD <douglas.raillard@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	"open list:TRACING" <linux-kernel@vger.kernel.org>,
	"open list:TRACING" <linux-trace-kernel@vger.kernel.org>
Subject: Re: [PATCH] rcu: Fix rcu_torture_read ftrace event
Date: Mon, 6 Mar 2023 18:24:46 +0530	[thread overview]
Message-ID: <9f3a25be-723c-3be0-94bd-820707c80656@quicinc.com> (raw)
In-Reply-To: <20230306122744.236790-1-douglas.raillard@arm.com>



On 3/6/2023 5:57 PM, Douglas RAILLARD wrote:
> From: Douglas Raillard <douglas.raillard@arm.com>
> 
> Fix the rcutorturename field so that its size is correctly reported in
> the text format embedded in trace.dat files. As it stands, it is
> reported as being of size 1:
> 
>      field:char rcutorturename[8];   offset:8;       size:1; signed:0;
> 
> Signed-off-by: Douglas Raillard <douglas.raillard@arm.com>
> ---
>   include/trace/events/rcu.h | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/trace/events/rcu.h b/include/trace/events/rcu.h
> index 90b2fb0292cb..012fa0d171b2 100644
> --- a/include/trace/events/rcu.h
> +++ b/include/trace/events/rcu.h
> @@ -768,7 +768,7 @@ TRACE_EVENT_RCU(rcu_torture_read,
>   	TP_ARGS(rcutorturename, rhp, secs, c_old, c),
>   
>   	TP_STRUCT__entry(
> -		__field(char, rcutorturename[RCUTORTURENAME_LEN])
> +		__array(char, rcutorturename, RCUTORTURENAME_LEN)

Reviewed-by: Mukesh Ojha <quic_mojha@quicinc.com>

-Mukesh

>   		__field(struct rcu_head *, rhp)
>   		__field(unsigned long, secs)
>   		__field(unsigned long, c_old)

  reply	other threads:[~2023-03-06 12:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 12:27 [PATCH] rcu: Fix rcu_torture_read ftrace event Douglas RAILLARD
2023-03-06 12:54 ` Mukesh Ojha [this message]
2023-03-20 15:20 ` Steven Rostedt
2023-03-20 16:58   ` Paul E. McKenney
2023-03-20 17:36     ` Steven Rostedt
2023-03-20 18:49       ` Paul E. McKenney

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=9f3a25be-723c-3be0-94bd-820707c80656@quicinc.com \
    --to=quic_mojha@quicinc.com \
    --cc=douglas.raillard@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --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