arch/sparc/Kconfig.debug

Source file repositories/reference/linux-study-clean/arch/sparc/Kconfig.debug

File Facts

System: Linux kernel
Corpus path: arch/sparc/Kconfig.debug
Extension: .debug
Size: 735 bytes
Lines: 28
Domain: Architecture Layer
Bucket: arch/sparc
Inferred role: Architecture Layer: arch/sparc
Status: atlas-only

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

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

config DEBUG_DCFLUSH
	bool "D-cache flush debugging"
	depends on SPARC64 && DEBUG_KERNEL

config MCOUNT
	bool
	depends on SPARC64
	depends on FUNCTION_TRACER
	select ARCH_WANT_FRAME_POINTERS
	select FRAME_POINTER
	default y

config HAVE_HARDLOCKUP_DETECTOR_SPARC64
	bool
	depends on HAVE_NMI
	select HARDLOCKUP_DETECTOR_SPARC64
	help
	  Sparc64 hardlockup detector is the last one developed before adding
	  the common infrastructure for handling hardlockup detectors. It is
	  always built. It does _not_ use the common command line parameters
	  and sysctl interface, except for /proc/sys/kernel/nmi_watchdog.

config HARDLOCKUP_DETECTOR_SPARC64
	bool
	depends on HAVE_HARDLOCKUP_DETECTOR_SPARC64

Annotation

Atlas domain: Architecture Layer / arch/sparc.
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.