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

[Nick Alcock]

On 30 Oct 2023, Kris Van Hees via DTrace-devel told this:

> 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>

Reviewed-by: Nick Alcock <nick.alcock at oracle.com>

with one footling caveat

> +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

Usually one would not repeat the option name but rather say "This option
generates a file in the build tree", or wherever this file is, and
probably also say what it's called :)

-- 
NULL && (void)