arch/powerpc/include/asm/cpufeature.h
Source file repositories/reference/linux-study-clean/arch/powerpc/include/asm/cpufeature.h
File Facts
- System
- Linux kernel
- Corpus path
arch/powerpc/include/asm/cpufeature.h- Extension
.h- Size
- 1068 bytes
- Lines
- 38
- Domain
- Architecture Layer
- Bucket
- arch/powerpc
- 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
asm/cputable.h
Detected Declarations
function module_cpu_feature_match
Annotated Snippet
#ifndef __ASM_POWERPC_CPUFEATURE_H
#define __ASM_POWERPC_CPUFEATURE_H
#include <asm/cputable.h>
/* Keep these in step with powerpc/include/asm/cputable.h */
#define MAX_CPU_FEATURES (2 * 32)
/*
* Currently we don't have a need for any of the feature bits defined in
* cpu_user_features. When we do, they should be defined such as:
*
* #define PPC_MODULE_FEATURE_32 (ilog2(PPC_FEATURE_32))
*/
#define PPC_MODULE_FEATURE_VEC_CRYPTO (32 + ilog2(PPC_FEATURE2_VEC_CRYPTO))
#define PPC_MODULE_FEATURE_P10 (32 + ilog2(PPC_FEATURE2_ARCH_3_1))
#define cpu_feature(x) (x)
static inline bool cpu_have_feature(unsigned int num)
{
if (num < 32)
return !!(cur_cpu_spec->cpu_user_features & 1UL << num);
else
return !!(cur_cpu_spec->cpu_user_features2 & 1UL << (num - 32));
}
#endif /* __ASM_POWERPC_CPUFEATURE_H */
Annotation
- Immediate include surface: `asm/cputable.h`.
- Detected declarations: `function module_cpu_feature_match`.
- Atlas domain: Architecture Layer / arch/powerpc.
- 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.