kernel/livepatch/Kconfig

Source file repositories/reference/linux-study-clean/kernel/livepatch/Kconfig

File Facts

System: Linux kernel
Corpus path: kernel/livepatch/Kconfig
Extension: [no extension]
Size: 836 bytes
Lines: 33
Domain: Core OS
Bucket: Scheduler, Processes, Timers, Sync, And Syscalls
Inferred role: Core OS: build/configuration rule
Status: atlas-only

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0-only
config HAVE_LIVEPATCH
	bool
	help
	  Arch supports kernel live patching

config LIVEPATCH
	bool "Kernel Live Patching"
	depends on DYNAMIC_FTRACE_WITH_REGS || DYNAMIC_FTRACE_WITH_ARGS
	depends on MODULES
	depends on SYSFS
	depends on KALLSYMS_ALL
	depends on HAVE_LIVEPATCH
	depends on !TRIM_UNUSED_KSYMS
	help
	  Say Y here if you want to support kernel live patching.
	  This option has no runtime impact until a kernel "patch"
	  module uses the interface provided by this option to register
	  a patch, causing calls to patched functions to be redirected
	  to new function code contained in the patch module.

config HAVE_KLP_BUILD
	bool
	help
	  Arch supports klp-build

config KLP_BUILD
	def_bool y
	depends on LIVEPATCH && HAVE_KLP_BUILD
	select OBJTOOL
	help
	  Enable klp-build support

Annotation

Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
Implementation status: atlas-only.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.