include/linux/kdb.h

File Facts

System

Linux kernel

Corpus path

include/linux/kdb.h

Extension

.h

Size

7836 bytes

Lines

240

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/list.h
• linux/smp.h
• linux/init.h
• linux/sched.h
• linux/atomic.h

Detected Declarations

• enum kdb_msgsrc
• function kdb_process_cpu
• function kdb_printf_on_this_cpu
• function __printf
• function kdb_init
• function kdb_unregister

Annotated Snippet

static inline __printf(1, 2) int kdb_printf(const char *fmt, ...) { return 0; }
static inline void kdb_init(int level) {}
static inline int kdb_register(kdbtab_t *cmd) { return 0; }
static inline void kdb_unregister(kdbtab_t *cmd) {}

static inline bool kdb_printf_on_this_cpu(void) { return false; }

#endif	/* CONFIG_KGDB_KDB */
enum {
	KDB_NOT_INITIALIZED,
	KDB_INIT_EARLY,
	KDB_INIT_FULL,
};

extern int kdbgetintenv(const char *, int *);
extern int kdb_set(int, const char **);
int kdb_lsmod(int argc, const char **argv);

#endif	/* !_KDB_H */

Annotation

• Immediate include surface: `linux/list.h`, `linux/smp.h`, `linux/init.h`, `linux/sched.h`, `linux/atomic.h`.
• Detected declarations: `enum kdb_msgsrc`, `function kdb_process_cpu`, `function kdb_printf_on_this_cpu`, `function __printf`, `function kdb_init`, `function kdb_unregister`.
• Atlas domain: Core OS / Core Kernel Interface.
• Implementation status: source implementation candidate.

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.