From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
bpf@vger.kernel.org, Sven Schnelle <svens@linux.ibm.com>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH v3 5/9] tracing/probes: Support BTF field access from $retval
Date: Thu, 27 Jul 2023 07:53:42 +0900 [thread overview]
Message-ID: <20230727075342.43f600a1850810f6e1dd6c2e@kernel.org> (raw)
In-Reply-To: <169037644255.607919.6218637643155663128.stgit@devnote2>
On Wed, 26 Jul 2023 22:00:42 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
>
> -static const struct btf_param *find_btf_func_param(const char *funcname, s32 *nr,
> - struct btf **btf_p, bool tracepoint)
> +static int query_btf_context(struct traceprobe_parse_context *ctx)
> {
> return ERR_PTR(-EOPNOTSUPP);
Oops, kernel test bot reported this is wrong. I have to remove ERR_PTR().
Thanks,
> }
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2023-07-26 22:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 12:59 [PATCH v3 0/9] tracing: Improbe BTF support on probe events Masami Hiramatsu (Google)
2023-07-26 13:00 ` [PATCH v3 1/9] tracing/probes: Support BTF argument on module functions Masami Hiramatsu (Google)
2023-07-26 13:00 ` [PATCH v3 2/9] bpf/btf: tracing: Move finding func-proto API and getting func-param API to BTF Masami Hiramatsu (Google)
2023-07-26 13:00 ` [PATCH v3 3/9] bpf/btf: Add a function to search a member of a struct/union Masami Hiramatsu (Google)
2023-07-27 15:39 ` Alexei Starovoitov
2023-07-28 0:09 ` Masami Hiramatsu
2023-07-26 13:00 ` [PATCH v3 4/9] tracing/probes: Support BTF based data structure field access Masami Hiramatsu (Google)
2023-07-26 13:00 ` [PATCH v3 5/9] tracing/probes: Support BTF field access from $retval Masami Hiramatsu (Google)
2023-07-26 22:53 ` Masami Hiramatsu [this message]
2023-07-27 1:59 ` [PATCH 5/9 v3.1] " Masami Hiramatsu (Google)
2023-07-26 13:00 ` [PATCH v3 6/9] tracing/probes: Add string type check with BTF Masami Hiramatsu (Google)
2023-07-26 13:01 ` [PATCH v3 7/9] tracing/fprobe-event: Assume fprobe is a return event by $retval Masami Hiramatsu (Google)
2023-07-26 13:01 ` [PATCH v3 8/9] selftests/ftrace: Add BTF fields access testcases Masami Hiramatsu (Google)
2023-07-26 13:01 ` [PATCH v3 9/9] Documentation: tracing: Update fprobe event example with BTF field Masami Hiramatsu (Google)
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=20230727075342.43f600a1850810f6e1dd6c2e@kernel.org \
--to=mhiramat@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=rostedt@goodmis.org \
--cc=svens@linux.ibm.com \
/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).