[DTrace-devel] [PATCH 2/5] module: add CONFIG_BUILTIN_RANGES option

[Kris Van Hees]

The CONFIG_BUILTIN_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 at oracle.com>
---
 kernel/module/Kconfig | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/kernel/module/Kconfig b/kernel/module/Kconfig
index 33a2e991f608..5982389f0b09 100644
--- a/kernel/module/Kconfig
+++ b/kernel/module/Kconfig
@@ -389,4 +389,17 @@ config MODULES_TREE_LOOKUP
 	def_bool y
 	depends on PERF_EVENTS || TRACING || CFI_CLANG
 
+config BUILTIN_RANGES
+	bool "Generate address ramge information for builtin modules"
+	depends on 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 synbols by module name and symbol name regardless of whether
+	  the module is configured as loadable or not.
+
+	  BUILTIN_RANGES generates a file that associates offset ranges (per
+	  ELF section) with the module(s) they below to.  It also records an
+	  anchor symbol to determine the load address of the section.
+
 endif # MODULES
-- 
2.39.2