linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.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 v7 04/11] tracing/probes: Add tracepoint support on fprobe_events
Date: Thu, 27 Apr 2023 13:59:03 +0200	[thread overview]
Message-ID: <ZEpjh8ZfZMch2Av/@krava> (raw)
In-Reply-To: <168255830406.2565678.710162679499561673.stgit@mhiramat.roam.corp.google.com>

On Thu, Apr 27, 2023 at 10:18:24AM +0900, Masami Hiramatsu (Google) wrote:

SNIP

>  	ret = traceprobe_parse_probe_arg(&ep->tp, i, argv[i], flags);
> diff --git a/kernel/trace/trace_fprobe.c b/kernel/trace/trace_fprobe.c
> index 0049d9ef2402..7c8be8a3616f 100644
> --- a/kernel/trace/trace_fprobe.c
> +++ b/kernel/trace/trace_fprobe.c
> @@ -9,6 +9,7 @@
>  #include <linux/module.h>
>  #include <linux/rculist.h>
>  #include <linux/security.h>
> +#include <linux/tracepoint.h>
>  #include <linux/uaccess.h>
>  
>  #include "trace_dynevent.h"
> @@ -17,6 +18,7 @@
>  #include "trace_probe_tmpl.h"
>  
>  #define FPROBE_EVENT_SYSTEM "fprobes"
> +#define TRACEPOINT_EVENT_SYSTEM "tracepoints"

so the created tracepoints go under 'events/tracepoints' directory,
should the name be more fprobe specific? like under 'events/fprobe/tracepoints' ?

jirka

>  #define RETHOOK_MAXACTIVE_MAX 4096
>  
>  static int trace_fprobe_create(const char *raw_command);
> @@ -41,6 +43,8 @@ struct trace_fprobe {
>  	struct dyn_event	devent;
>  	struct fprobe		fp;
>  	const char		*symbol;
> +	struct tracepoint	*tpoint;
> +	struct module		*mod;
>  	struct trace_probe	tp;
>  };
>  
> @@ -68,6 +72,11 @@ static bool trace_fprobe_is_return(struct trace_fprobe *tf)
>  	return tf->fp.exit_handler != NULL;
>  }
>  
> +static bool trace_fprobe_is_tracepoint(struct trace_fprobe *tf)
> +{
> +	return tf->tpoint != NULL;
> +}
> +

SNIP

  reply	other threads:[~2023-04-27 11:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27  1:17 [PATCH v7 00/11] tracing: Add fprobe events Masami Hiramatsu (Google)
2023-04-27  1:17 ` [PATCH v7 01/11] fprobe: Pass return address to the handlers Masami Hiramatsu (Google)
2023-04-27  1:18 ` [PATCH v7 02/11] tracing/probes: Add fprobe events for tracing function entry and exit Masami Hiramatsu (Google)
2023-04-27  1:18 ` [PATCH v7 03/11] selftests/ftrace: Add fprobe related testcases Masami Hiramatsu (Google)
2023-04-27  1:18 ` [PATCH v7 04/11] tracing/probes: Add tracepoint support on fprobe_events Masami Hiramatsu (Google)
2023-04-27 11:59   ` Jiri Olsa [this message]
2023-04-28  1:22     ` Masami Hiramatsu
2023-04-27  1:18 ` [PATCH v7 05/11] tracing/probes: Move event parameter fetching code to common parser Masami Hiramatsu (Google)
2023-04-27  1:18 ` [PATCH v7 06/11] tracing/probes: Support function parameters if BTF is available Masami Hiramatsu (Google)
2023-04-27  1:18 ` [PATCH v7 07/11] tracing/probes: Add $$args meta argument for all function args Masami Hiramatsu (Google)
2023-04-27  1:19 ` [PATCH v7 08/11] tracing/probes: Add BTF retval type support Masami Hiramatsu (Google)
2023-05-01 10:11   ` Masami Hiramatsu
2023-04-27  1:19 ` [PATCH v7 09/11] selftests/ftrace: Add tracepoint probe test case Masami Hiramatsu (Google)
2023-04-27  1:19 ` [PATCH v7 10/11] selftests/ftrace: Add BTF arguments test cases Masami Hiramatsu (Google)
2023-04-27  1:19 ` [PATCH v7 11/11] Documentation: tracing/probes: Add fprobe event tracing document Masami Hiramatsu (Google)
2023-04-27 11:58 ` [PATCH v7 00/11] tracing: Add fprobe events Jiri Olsa
2023-04-28  0:40   ` 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=ZEpjh8ZfZMch2Av/@krava \
    --to=olsajiri@gmail.com \
    --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=rostedt@goodmis.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).