[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z8pIiM2Z_jtNNUhN@google.com>
Date: Thu, 6 Mar 2025 17:14:48 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Ian Rogers <irogers@...gle.com>
Cc: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Kan Liang <kan.liang@...ux.intel.com>,
John Garry <john.g.garry@...cle.com>, Will Deacon <will@...nel.org>,
James Clark <james.clark@...aro.org>,
Mike Leach <mike.leach@...aro.org>, Leo Yan <leo.yan@...ux.dev>,
guoren <guoren@...nel.org>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Charlie Jenkins <charlie@...osinc.com>,
Bibo Mao <maobibo@...ngson.cn>, Huacai Chen <chenhuacai@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Jiri Slaby <jirislaby@...nel.org>,
Björn Töpel <bjorn@...osinc.com>,
Howard Chu <howardchu95@...il.com>, linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
"linux-csky@...r.kernel.org" <linux-csky@...r.kernel.org>,
linux-riscv@...ts.infradead.org, Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v4 02/11] perf dso: kernel-doc for enum dso_binary_type
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@...gle.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
>
Powered by blists - more mailing lists