From: Kris Van Hees <kris.van.hees@oracle.com>
To: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-modules@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Cc: Kris Van Hees <kris.van.hees@oracle.com>,
Nick Alcock <nick.alcock@oracle.com>,
Alan Maguire <alan.maguire@oracle.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Jiri Olsa <olsajiri@gmail.com>,
Elena Zannoni <elena.zannoni@oracle.com>
Subject: [PATCH v3 2/6] trace: add CONFIG_BUILTIN_MODULE_RANGES option
Date: Fri, 17 May 2024 00:28:35 -0400 [thread overview]
Message-ID: <20240517042839.544650-3-kris.van.hees@oracle.com> (raw)
In-Reply-To: <20240517042839.544650-1-kris.van.hees@oracle.com>
The CONFIG_BUILTIN_MODULE_RANGES option controls whether offset range data
is generated for kernel modules that are built into the kernel image.
Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
Reviewed-by: Alan Maguire <alan.maguire@oracle.com>
---
Changes since v2:
- Add explicit dependency on FTRACE for CONFIG_BUILTIN_MODULE_RANGES
---
kernel/trace/Kconfig | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index 47345bf1d4a9f..d0c82b4b3a61e 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -188,6 +188,24 @@ menuconfig FTRACE
if FTRACE
+config BUILTIN_MODULE_RANGES
+ bool "Generate address range information for builtin modules"
+ depends on FTRACE
+ select VMLINUX_MAP
+ help
+ When modules are built into the kernel, there will be no module name
+ associated with its symbols in /proc/kallsyms. Tracers may want to
+ identify symbols by module name and symbol name regardless of whether
+ the module is configured as loadable or not.
+
+ This option generates modules.builtin.ranges in the build tree with
+ offset ranges (per ELF section) for the module(s) they belong to.
+ It also records an anchor symbol to determine the load address of the
+ section.
+
+ It is fully compatible with CONFIG_RANDOMIZE_BASE and similar late-
+ address-modification options.
+
config BOOTTIME_TRACING
bool "Boot-time Tracing support"
depends on TRACING
--
2.43.0
next prev parent reply other threads:[~2024-05-17 4:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 4:28 [PATCH v3 0/6] Generate address range data for built-in modules Kris Van Hees
2024-05-17 4:28 ` [PATCH v3 1/6] kbuild: add mod(name,file)_flags to assembler flags for module objects Kris Van Hees
2024-05-17 4:28 ` Kris Van Hees [this message]
2024-05-20 9:29 ` [PATCH v3 2/6] trace: add CONFIG_BUILTIN_MODULE_RANGES option Masahiro Yamada
2024-05-20 9:38 ` Masahiro Yamada
2024-05-17 4:28 ` [PATCH v3 3/6] kbuild: generate a linker map for vmlinux.o Kris Van Hees
2024-05-17 4:28 ` [PATCH v3 4/6] module: script to generate offset ranges for builtin modules Kris Van Hees
2024-05-20 16:53 ` Masahiro Yamada
2024-06-06 19:02 ` Kris Van Hees
2024-05-17 4:28 ` [PATCH v3 5/6] kbuild: generate modules.builtin.ranges when linking the kernel Kris Van Hees
2024-05-17 4:28 ` [PATCH v3 6/6] module: add install target for modules.builtin.ranges Kris Van Hees
2024-05-20 9:10 ` Masahiro Yamada
-- strict thread matches above, loose matches on Subject: below --
2024-05-24 18:25 kernel test robot
2024-05-27 0:58 ` kernel test robot
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=20240517042839.544650-3-kris.van.hees@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=alan.maguire@oracle.com \
--cc=elena.zannoni@oracle.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nick.alcock@oracle.com \
--cc=olsajiri@gmail.com \
--cc=rostedt@goodmis.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.