From: Steven Rostedt <rostedt@goodmis.org>
To: Douglas Raillard <douglas.raillard@arm.com>
Cc: linux-trace-devel@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Takaya Saeki <takayas@google.com>,
Ian Rogers <irogers@google.com>,
aahringo@redhat.com
Subject: Re: [PATCH 0/5] trace-cmd: Use BTF to parse function arguments
Date: Mon, 4 Aug 2025 10:36:22 -0400 [thread overview]
Message-ID: <20250804103622.3b3762e6@gandalf.local.home> (raw)
In-Reply-To: <8e75d9d2-8fa2-4232-a00e-2e9bc20d3701@arm.com>
On Mon, 4 Aug 2025 15:28:58 +0100
Douglas Raillard <douglas.raillard@arm.com> wrote:
> Sounds like a good idea. If you want to support passing BTF at report time to supplement a BTF-less trace.dat,
> it would make sense to also support getting BTF from the ELF section so that people can pass the real
> vmlinux file directly (not the BTF blob in sysfs, the actual ELF vmlinux from Kbuild).
>
> It seems libbpf allows to do that with bpf_object__open_file():
> https://docs.ebpf.io/ebpf-library/libbpf/userspace/bpf_object__open_file/
>
Yeah, but then it adds a dependency that I'm trying to limit.
Parsing elf files for sections is quite trivial. I've done that a lot. I
may just add a: --btf-elf /path/to/elf-file
-- Steve
prev parent reply other threads:[~2025-08-04 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 20:20 [PATCH 0/5] trace-cmd: Use BTF to parse function arguments Steven Rostedt
2025-07-31 20:20 ` [PATCH 1/5] libtracecmd: Remove "compress" parameter from save_string_section() Steven Rostedt
2025-07-31 20:20 ` [PATCH 2/5] libtracecmd: Remove "compress" parameter from tcmd_out_compress*() functions Steven Rostedt
2025-07-31 20:20 ` [PATCH 3/5] libtracecmd: Add write_compress_section_header() for writing compress sections Steven Rostedt
2025-07-31 20:20 ` [PATCH 4/5] trace-cmd record / report: Record BTF file if function arguments are recorded Steven Rostedt
2025-08-04 12:37 ` Douglas Raillard
2025-07-31 20:20 ` [PATCH 5/5] libtracecmd: Add printing of arguments for function graph tracer Steven Rostedt
2025-08-04 12:36 ` [PATCH 0/5] trace-cmd: Use BTF to parse function arguments Douglas Raillard
2025-08-04 12:45 ` Steven Rostedt
2025-08-04 14:28 ` Douglas Raillard
2025-08-04 14:36 ` 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=20250804103622.3b3762e6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=aahringo@redhat.com \
--cc=douglas.raillard@arm.com \
--cc=irogers@google.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=takayas@google.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).