arch/loongarch/include/uapi/asm/hwcap.h

File Facts

System

Linux kernel

Corpus path

arch/loongarch/include/uapi/asm/hwcap.h

Extension

.h

Size

848 bytes

Lines

25

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.

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

#ifndef _UAPI_ASM_HWCAP_H
#define _UAPI_ASM_HWCAP_H

/* HWCAP flags */
#define HWCAP_LOONGARCH_CPUCFG		(1 << 0)
#define HWCAP_LOONGARCH_LAM		(1 << 1)
#define HWCAP_LOONGARCH_UAL		(1 << 2)
#define HWCAP_LOONGARCH_FPU		(1 << 3)
#define HWCAP_LOONGARCH_LSX		(1 << 4)
#define HWCAP_LOONGARCH_LASX		(1 << 5)
#define HWCAP_LOONGARCH_CRC32		(1 << 6)
#define HWCAP_LOONGARCH_COMPLEX		(1 << 7)
#define HWCAP_LOONGARCH_CRYPTO		(1 << 8)
#define HWCAP_LOONGARCH_LVZ		(1 << 9)
#define HWCAP_LOONGARCH_LBT_X86		(1 << 10)
#define HWCAP_LOONGARCH_LBT_ARM		(1 << 11)
#define HWCAP_LOONGARCH_LBT_MIPS	(1 << 12)
#define HWCAP_LOONGARCH_PTW		(1 << 13)
#define HWCAP_LOONGARCH_LSPW		(1 << 14)
#define HWCAP_LOONGARCH_SCQ		(1 << 15)
#define HWCAP_LOONGARCH_LAM_BH		(1 << 16)

#endif /* _UAPI_ASM_HWCAP_H */

Annotation

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