From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@kernel.org>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Kan Liang" <kan.liang@linux.intel.com>,
"John Garry" <john.g.garry@oracle.com>,
"Will Deacon" <will@kernel.org>,
"James Clark" <james.clark@linaro.org>,
"Mike Leach" <mike.leach@linaro.org>,
"Leo Yan" <leo.yan@linux.dev>, guoren <guoren@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Charlie Jenkins" <charlie@rivosinc.com>,
"Bibo Mao" <maobibo@loongson.cn>,
"Huacai Chen" <chenhuacai@kernel.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Howard Chu" <howardchu95@gmail.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"linux-csky@vger.kernel.org" <linux-csky@vger.kernel.org>,
linux-riscv@lists.infradead.org, "Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [PATCH v4 02/11] perf dso: kernel-doc for enum dso_binary_type
Date: Thu, 6 Mar 2025 17:14:48 -0800 [thread overview]
Message-ID: <Z8pIiM2Z_jtNNUhN@google.com> (raw)
In-Reply-To: <20250304050305.901167-3-irogers@google.com>
On Mon, Mar 03, 2025 at 09:02:56PM -0800, Ian Rogers wrote:
> There are many and non-obvious meanings to the dso_binary_type enum
> values. Add kernel-doc to speed interpretting their meanings.
>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/util/dso.h | 53 +++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 53 insertions(+)
>
> diff --git a/tools/perf/util/dso.h b/tools/perf/util/dso.h
> index dfd763a0bd9d..f3ca2a5e7670 100644
> --- a/tools/perf/util/dso.h
> +++ b/tools/perf/util/dso.h
> @@ -20,30 +20,83 @@ struct perf_env;
> #define DSO__NAME_KALLSYMS "[kernel.kallsyms]"
> #define DSO__NAME_KCORE "[kernel.kcore]"
>
> +/**
> + * enum dso_binary_type - The kind of DSO generally associated with a memory
> + * region (struct map).
> + */
Thanks for adding these comments!
> enum dso_binary_type {
> + /** @DSO_BINARY_TYPE__KALLSYMS: Symbols from /proc/kallsyms file. */
> DSO_BINARY_TYPE__KALLSYMS = 0,
> + /** @DSO_BINARY_TYPE__GUEST_KALLSYMS: Guest /proc/kallsyms file. */
> DSO_BINARY_TYPE__GUEST_KALLSYMS,
> + /** @DSO_BINARY_TYPE__VMLINUX: Path to guest kernel /boot/vmlinux file. */
> DSO_BINARY_TYPE__VMLINUX,
It's not for guest. Also I think the vmlinux file can come from
different places.
> + /** @DSO_BINARY_TYPE__GUEST_VMLINUX: Path to kernel /boot/vmlinux file. */
> DSO_BINARY_TYPE__GUEST_VMLINUX,
This is for guest. :)
Thanks,
Namhyung
> + /** @DSO_BINARY_TYPE__JAVA_JIT: Symbols from /tmp/perf.map file. */
> DSO_BINARY_TYPE__JAVA_JIT,
> + /**
> + * @DSO_BINARY_TYPE__DEBUGLINK: Debug file readable from the file path
> + * in the .gnu_debuglink ELF section of the dso.
> + */
> DSO_BINARY_TYPE__DEBUGLINK,
> + /**
> + * @DSO_BINARY_TYPE__BUILD_ID_CACHE: File named after buildid located in
> + * the buildid cache with an elf filename.
> + */
> DSO_BINARY_TYPE__BUILD_ID_CACHE,
> + /**
> + * @DSO_BINARY_TYPE__BUILD_ID_CACHE_DEBUGINFO: File named after buildid
> + * located in the buildid cache with a debug filename.
> + */
> DSO_BINARY_TYPE__BUILD_ID_CACHE_DEBUGINFO,
> + /**
> + * @DSO_BINARY_TYPE__FEDORA_DEBUGINFO: Debug file in /usr/lib/debug
> + * with .debug suffix.
> + */
> DSO_BINARY_TYPE__FEDORA_DEBUGINFO,
> + /** @DSO_BINARY_TYPE__UBUNTU_DEBUGINFO: Debug file in /usr/lib/debug. */
> DSO_BINARY_TYPE__UBUNTU_DEBUGINFO,
> + /**
> + * @DSO_BINARY_TYPE__MIXEDUP_UBUNTU_DEBUGINFO: dso__long_name debuginfo
> + * file in /usr/lib/debug/lib rather than the expected
> + * /usr/lib/debug/usr/lib.
> + */
> DSO_BINARY_TYPE__MIXEDUP_UBUNTU_DEBUGINFO,
> + /**
> + * @DSO_BINARY_TYPE__BUILDID_DEBUGINFO: File named after buildid located
> + * in /usr/lib/debug/.build-id/.
> + */
> DSO_BINARY_TYPE__BUILDID_DEBUGINFO,
> + /** @DSO_BINARY_TYPE__SYSTEM_PATH_DSO: A regular executable/shared-object file. */
> DSO_BINARY_TYPE__SYSTEM_PATH_DSO,
> + /** @DSO_BINARY_TYPE__GUEST_KMODULE: Guest kernel module .ko file. */
> DSO_BINARY_TYPE__GUEST_KMODULE,
> + /** @DSO_BINARY_TYPE__GUEST_KMODULE_COMP: Guest kernel module .ko.gz file. */
> DSO_BINARY_TYPE__GUEST_KMODULE_COMP,
> + /** @DSO_BINARY_TYPE__SYSTEM_PATH_KMODULE: Kernel module .ko file. */
> DSO_BINARY_TYPE__SYSTEM_PATH_KMODULE,
> + /** @DSO_BINARY_TYPE__SYSTEM_PATH_KMODULE_COMP: Kernel module .ko.gz file. */
> DSO_BINARY_TYPE__SYSTEM_PATH_KMODULE_COMP,
> + /** @DSO_BINARY_TYPE__KCORE: /proc/kcore file. */
> DSO_BINARY_TYPE__KCORE,
> + /** @DSO_BINARY_TYPE__GUEST_KCORE: Guest /proc/kcore file. */
> DSO_BINARY_TYPE__GUEST_KCORE,
> + /**
> + * @DSO_BINARY_TYPE__OPENEMBEDDED_DEBUGINFO: Openembedded/Yocto -dbg
> + * package debug info.
> + */
> DSO_BINARY_TYPE__OPENEMBEDDED_DEBUGINFO,
> + /** @DSO_BINARY_TYPE__BPF_PROG_INFO: jitted BPF code. */
> DSO_BINARY_TYPE__BPF_PROG_INFO,
> + /** @DSO_BINARY_TYPE__BPF_IMAGE: jitted BPF trampoline or dispatcher code. */
> DSO_BINARY_TYPE__BPF_IMAGE,
> + /**
> + * @DSO_BINARY_TYPE__OOL: out of line code such as kprobe-replaced
> + * instructions or optimized kprobes or ftrace trampolines.
> + */
> DSO_BINARY_TYPE__OOL,
> + /** @DSO_BINARY_TYPE__NOT_FOUND: Unknown DSO kind. */
> DSO_BINARY_TYPE__NOT_FOUND,
> };
>
> --
> 2.48.1.711.g2feabab25a-goog
>
WARNING: multiple messages have this Message-ID (diff)
From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@kernel.org>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Kan Liang" <kan.liang@linux.intel.com>,
"John Garry" <john.g.garry@oracle.com>,
"Will Deacon" <will@kernel.org>,
"James Clark" <james.clark@linaro.org>,
"Mike Leach" <mike.leach@linaro.org>,
"Leo Yan" <leo.yan@linux.dev>, guoren <guoren@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Charlie Jenkins" <charlie@rivosinc.com>,
"Bibo Mao" <maobibo@loongson.cn>,
"Huacai Chen" <chenhuacai@kernel.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Howard Chu" <howardchu95@gmail.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"linux-csky@vger.kernel.org" <linux-csky@vger.kernel.org>,
linux-riscv@lists.infradead.org, "Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [PATCH v4 02/11] perf dso: kernel-doc for enum dso_binary_type
Date: Thu, 6 Mar 2025 17:14:48 -0800 [thread overview]
Message-ID: <Z8pIiM2Z_jtNNUhN@google.com> (raw)
In-Reply-To: <20250304050305.901167-3-irogers@google.com>
On Mon, Mar 03, 2025 at 09:02:56PM -0800, Ian Rogers wrote:
> There are many and non-obvious meanings to the dso_binary_type enum
> values. Add kernel-doc to speed interpretting their meanings.
>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/util/dso.h | 53 +++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 53 insertions(+)
>
> diff --git a/tools/perf/util/dso.h b/tools/perf/util/dso.h
> index dfd763a0bd9d..f3ca2a5e7670 100644
> --- a/tools/perf/util/dso.h
> +++ b/tools/perf/util/dso.h
> @@ -20,30 +20,83 @@ struct perf_env;
> #define DSO__NAME_KALLSYMS "[kernel.kallsyms]"
> #define DSO__NAME_KCORE "[kernel.kcore]"
>
> +/**
> + * enum dso_binary_type - The kind of DSO generally associated with a memory
> + * region (struct map).
> + */
Thanks for adding these comments!
> enum dso_binary_type {
> + /** @DSO_BINARY_TYPE__KALLSYMS: Symbols from /proc/kallsyms file. */
> DSO_BINARY_TYPE__KALLSYMS = 0,
> + /** @DSO_BINARY_TYPE__GUEST_KALLSYMS: Guest /proc/kallsyms file. */
> DSO_BINARY_TYPE__GUEST_KALLSYMS,
> + /** @DSO_BINARY_TYPE__VMLINUX: Path to guest kernel /boot/vmlinux file. */
> DSO_BINARY_TYPE__VMLINUX,
It's not for guest. Also I think the vmlinux file can come from
different places.
> + /** @DSO_BINARY_TYPE__GUEST_VMLINUX: Path to kernel /boot/vmlinux file. */
> DSO_BINARY_TYPE__GUEST_VMLINUX,
This is for guest. :)
Thanks,
Namhyung
> + /** @DSO_BINARY_TYPE__JAVA_JIT: Symbols from /tmp/perf.map file. */
> DSO_BINARY_TYPE__JAVA_JIT,
> + /**
> + * @DSO_BINARY_TYPE__DEBUGLINK: Debug file readable from the file path
> + * in the .gnu_debuglink ELF section of the dso.
> + */
> DSO_BINARY_TYPE__DEBUGLINK,
> + /**
> + * @DSO_BINARY_TYPE__BUILD_ID_CACHE: File named after buildid located in
> + * the buildid cache with an elf filename.
> + */
> DSO_BINARY_TYPE__BUILD_ID_CACHE,
> + /**
> + * @DSO_BINARY_TYPE__BUILD_ID_CACHE_DEBUGINFO: File named after buildid
> + * located in the buildid cache with a debug filename.
> + */
> DSO_BINARY_TYPE__BUILD_ID_CACHE_DEBUGINFO,
> + /**
> + * @DSO_BINARY_TYPE__FEDORA_DEBUGINFO: Debug file in /usr/lib/debug
> + * with .debug suffix.
> + */
> DSO_BINARY_TYPE__FEDORA_DEBUGINFO,
> + /** @DSO_BINARY_TYPE__UBUNTU_DEBUGINFO: Debug file in /usr/lib/debug. */
> DSO_BINARY_TYPE__UBUNTU_DEBUGINFO,
> + /**
> + * @DSO_BINARY_TYPE__MIXEDUP_UBUNTU_DEBUGINFO: dso__long_name debuginfo
> + * file in /usr/lib/debug/lib rather than the expected
> + * /usr/lib/debug/usr/lib.
> + */
> DSO_BINARY_TYPE__MIXEDUP_UBUNTU_DEBUGINFO,
> + /**
> + * @DSO_BINARY_TYPE__BUILDID_DEBUGINFO: File named after buildid located
> + * in /usr/lib/debug/.build-id/.
> + */
> DSO_BINARY_TYPE__BUILDID_DEBUGINFO,
> + /** @DSO_BINARY_TYPE__SYSTEM_PATH_DSO: A regular executable/shared-object file. */
> DSO_BINARY_TYPE__SYSTEM_PATH_DSO,
> + /** @DSO_BINARY_TYPE__GUEST_KMODULE: Guest kernel module .ko file. */
> DSO_BINARY_TYPE__GUEST_KMODULE,
> + /** @DSO_BINARY_TYPE__GUEST_KMODULE_COMP: Guest kernel module .ko.gz file. */
> DSO_BINARY_TYPE__GUEST_KMODULE_COMP,
> + /** @DSO_BINARY_TYPE__SYSTEM_PATH_KMODULE: Kernel module .ko file. */
> DSO_BINARY_TYPE__SYSTEM_PATH_KMODULE,
> + /** @DSO_BINARY_TYPE__SYSTEM_PATH_KMODULE_COMP: Kernel module .ko.gz file. */
> DSO_BINARY_TYPE__SYSTEM_PATH_KMODULE_COMP,
> + /** @DSO_BINARY_TYPE__KCORE: /proc/kcore file. */
> DSO_BINARY_TYPE__KCORE,
> + /** @DSO_BINARY_TYPE__GUEST_KCORE: Guest /proc/kcore file. */
> DSO_BINARY_TYPE__GUEST_KCORE,
> + /**
> + * @DSO_BINARY_TYPE__OPENEMBEDDED_DEBUGINFO: Openembedded/Yocto -dbg
> + * package debug info.
> + */
> DSO_BINARY_TYPE__OPENEMBEDDED_DEBUGINFO,
> + /** @DSO_BINARY_TYPE__BPF_PROG_INFO: jitted BPF code. */
> DSO_BINARY_TYPE__BPF_PROG_INFO,
> + /** @DSO_BINARY_TYPE__BPF_IMAGE: jitted BPF trampoline or dispatcher code. */
> DSO_BINARY_TYPE__BPF_IMAGE,
> + /**
> + * @DSO_BINARY_TYPE__OOL: out of line code such as kprobe-replaced
> + * instructions or optimized kprobes or ftrace trampolines.
> + */
> DSO_BINARY_TYPE__OOL,
> + /** @DSO_BINARY_TYPE__NOT_FOUND: Unknown DSO kind. */
> DSO_BINARY_TYPE__NOT_FOUND,
> };
>
> --
> 2.48.1.711.g2feabab25a-goog
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-03-07 1:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 5:02 [PATCH v4 00/11] perf: Support multiple system call tables in the build Ian Rogers
2025-03-04 5:02 ` Ian Rogers
2025-03-04 5:02 ` [PATCH v4 01/11] perf dso: Move libunwind dso_data variables into ifdef Ian Rogers
2025-03-04 5:02 ` Ian Rogers
2025-03-05 17:52 ` Arnaldo Carvalho de Melo
2025-03-05 17:52 ` Arnaldo Carvalho de Melo
2025-03-04 5:02 ` [PATCH v4 02/11] perf dso: kernel-doc for enum dso_binary_type Ian Rogers
2025-03-04 5:02 ` Ian Rogers
2025-03-05 17:54 ` Arnaldo Carvalho de Melo
2025-03-05 17:54 ` Arnaldo Carvalho de Melo
2025-03-07 1:14 ` Namhyung Kim [this message]
2025-03-07 1:14 ` Namhyung Kim
2025-03-04 5:02 ` [PATCH v4 03/11] perf syscalltbl: Remove syscall_table.h Ian Rogers
2025-03-04 5:02 ` Ian Rogers
2025-03-04 5:02 ` [PATCH v4 04/11] perf trace: Reorganize syscalls Ian Rogers
2025-03-04 5:02 ` Ian Rogers
2025-03-04 5:02 ` [PATCH v4 05/11] perf syscalltbl: Remove struct syscalltbl Ian Rogers
2025-03-04 5:02 ` Ian Rogers
2025-03-04 5:03 ` [PATCH v4 06/11] perf dso: Add support for reading the e_machine type for a dso Ian Rogers
2025-03-04 5:03 ` Ian Rogers
2025-03-07 1:22 ` Namhyung Kim
2025-03-07 1:22 ` Namhyung Kim
2025-03-07 5:30 ` Ian Rogers
2025-03-07 5:30 ` Ian Rogers
2025-03-04 5:03 ` [PATCH v4 07/11] perf thread: Add support for reading the e_machine type for a thread Ian Rogers
2025-03-04 5:03 ` Ian Rogers
2025-03-04 5:03 ` [PATCH v4 08/11] perf trace beauty: Add syscalltbl.sh generating all system call tables Ian Rogers
2025-03-04 5:03 ` Ian Rogers
2025-03-04 5:03 ` [PATCH v4 09/11] perf syscalltbl: Use lookup table containing multiple architectures Ian Rogers
2025-03-04 5:03 ` Ian Rogers
2025-03-04 5:03 ` [PATCH v4 10/11] perf build: Remove Makefile.syscalls Ian Rogers
2025-03-04 5:03 ` Ian Rogers
2025-03-04 5:03 ` [PATCH v4 11/11] perf syscalltbl: Mask off ABI type for MIPS system calls Ian Rogers
2025-03-04 5:03 ` Ian Rogers
2025-03-04 7:04 ` [PATCH v4 00/11] perf: Support multiple system call tables in the build Ian Rogers
2025-03-04 7:04 ` Ian Rogers
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=Z8pIiM2Z_jtNNUhN@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=bjorn@rivosinc.com \
--cc=catalin.marinas@arm.com \
--cc=charlie@rivosinc.com \
--cc=chenhuacai@kernel.org \
--cc=guoren@kernel.org \
--cc=howardchu95@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jirislaby@kernel.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maobibo@loongson.cn \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.