linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Florent Revest <revest@chromium.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Will Deacon <will@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	bpf@vger.kernel.org
Subject: Re: [PATCH v9.1 07/11] tracing/probes: Add $$args meta argument for all function args
Date: Fri, 5 May 2023 17:48:56 -0400	[thread overview]
Message-ID: <20230505174856.04ca1e6a@gandalf.local.home> (raw)
In-Reply-To: <168299390127.3242086.2714570777321787734.stgit@mhiramat.roam.corp.google.com>

On Tue,  2 May 2023 11:18:21 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:

> From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> 
> Add the '$$args' meta fetch argument for function-entry probe events. This

Hmm, couldn't we just use $args ? That would be different from $arg1,
$arg2, etc.

The $$ to me would be either the bash pid of current, or perhaps it would
be just to use a dollar sign. I don't see the precedence of $$args being a
"full expand".

-- Steve


> will be expanded to the all arguments of the function and the tracepoint
> using BTF function argument information.
> 
> e.g.
>  #  echo 'p vfs_read $$args' >> dynamic_events
>  #  echo 'f vfs_write $$args' >> dynamic_events
>  #  echo 't sched_overutilized_tp $$args' >> dynamic_events
>  # cat dynamic_events
> p:kprobes/p_vfs_read_0 vfs_read file=file buf=buf count=count pos=pos
> f:fprobes/vfs_write__entry vfs_write file=file buf=buf count=count pos=pos
> t:tracepoints/sched_overutilized_tp sched_overutilized_tp rd=rd overutilized=overutilized
> 
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> ---

  reply	other threads:[~2023-05-05 21:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02  2:17 [PATCH v9.1 00/11] tracing: Add fprobe/tracepoint events Masami Hiramatsu (Google)
2023-05-02  2:17 ` [PATCH v9.1 01/11] fprobe: Pass return address to the handlers Masami Hiramatsu (Google)
2023-05-05 15:21   ` Steven Rostedt
2023-05-09 14:51     ` Masami Hiramatsu
2023-05-02  2:17 ` [PATCH v9.1 02/11] tracing/probes: Add fprobe events for tracing function entry and exit Masami Hiramatsu (Google)
2023-05-05 16:12   ` Steven Rostedt
2023-05-09 15:08     ` Masami Hiramatsu
2023-05-02  2:17 ` [PATCH v9.1 03/11] selftests/ftrace: Add fprobe related testcases Masami Hiramatsu (Google)
2023-05-02  2:17 ` [PATCH v9.1 04/11] tracing/probes: Add tracepoint support on fprobe_events Masami Hiramatsu (Google)
2023-05-02  2:18 ` [PATCH v9.1 05/11] tracing/probes: Move event parameter fetching code to common parser Masami Hiramatsu (Google)
2023-05-05 21:40   ` Steven Rostedt
2023-05-14  4:11     ` Masami Hiramatsu
2023-05-02  2:18 ` [PATCH v9.1 06/11] tracing/probes: Support function parameters if BTF is available Masami Hiramatsu (Google)
2023-05-02  2:18 ` [PATCH v9.1 07/11] tracing/probes: Add $$args meta argument for all function args Masami Hiramatsu (Google)
2023-05-05 21:48   ` Steven Rostedt [this message]
2023-05-14  3:02     ` Masami Hiramatsu
2023-05-02  2:18 ` [PATCH v9.1 08/11] tracing/probes: Add BTF retval type support Masami Hiramatsu (Google)
2023-05-02  2:18 ` [PATCH v9.1 09/11] selftests/ftrace: Add tracepoint probe test case Masami Hiramatsu (Google)
2023-05-02  2:18 ` [PATCH v9.1 10/11] selftests/ftrace: Add BTF arguments test cases Masami Hiramatsu (Google)
2023-05-02  2:18 ` [PATCH v9.1 11/11] Documentation: tracing/probes: Add fprobe event tracing document Masami Hiramatsu (Google)
2023-05-05 15:20   ` Steven Rostedt
2023-05-09 14:58     ` 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=20230505174856.04ca1e6a@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=martin.lau@linux.dev \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=revest@chromium.org \
    --cc=will@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).