arch/loongarch/include/asm/lbt.h

File Facts

System

Linux kernel

Corpus path

arch/loongarch/include/asm/lbt.h

Extension

.h

Size

2447 bytes

Lines

114

Domain

Architecture Layer

Bucket

arch/loongarch

Inferred role

Architecture Layer: implementation source

Status

source implementation candidate

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

Dependency Surface

• asm/cpu.h
• asm/current.h
• asm/loongarch.h
• asm/processor.h

Detected Declarations

• function is_lbt_enabled
• function is_lbt_owner
• function enable_lbt
• function disable_lbt
• function __own_lbt
• function own_lbt_inatomic
• function own_lbt
• function lose_lbt_inatomic
• function lose_lbt
• function init_lbt
• function own_lbt_inatomic

Annotated Snippet

static inline void own_lbt_inatomic(int restore) {}
static inline void lose_lbt_inatomic(int save, struct task_struct *tsk) {}
static inline void init_lbt(void) {}
static inline void lose_lbt(int save) {}
#endif

static inline int thread_lbt_context_live(void)
{
	if (!cpu_has_lbt)
		return 0;

	return test_thread_flag(TIF_LBT_CTX_LIVE);
}

#endif /* _ASM_LBT_H */

Annotation

• Immediate include surface: `asm/cpu.h`, `asm/current.h`, `asm/loongarch.h`, `asm/processor.h`.
• Detected declarations: `function is_lbt_enabled`, `function is_lbt_owner`, `function enable_lbt`, `function disable_lbt`, `function __own_lbt`, `function own_lbt_inatomic`, `function own_lbt`, `function lose_lbt_inatomic`, `function lose_lbt`, `function init_lbt`.
• Atlas domain: Architecture Layer / arch/loongarch.
• 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.