arch/s390/include/asm/insn-common-asm.h
Source file repositories/reference/linux-study-clean/arch/s390/include/asm/insn-common-asm.h
File Facts
- System
- Linux kernel
- Corpus path
arch/s390/include/asm/insn-common-asm.h- Extension
.h- Size
- 1186 bytes
- Lines
- 54
- Domain
- Architecture Layer
- Bucket
- arch/s390
- 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 __ASM_S390_INSN_COMMON_ASM_H
#define __ASM_S390_INSN_COMMON_ASM_H
#ifdef __ASSEMBLER__
/*
* GR_NUM - Retrieve general-purpose register number
*
* @opd: Operand to store register number
* @gr: String designation register in the format "%rN"
*/
.macro GR_NUM opd gr
\opd = 255
.irp rs,0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15
.ifc \gr,%r\rs
\opd = \rs
.endif
.endr
.if \opd == 255
\opd = \gr
.endif
.endm
/*
* VX_NUM - Retrieve vector register number
*
* @opd: Operand to store register number
* @vxr: String designation register in the format "%vN"
*
* The vector register number is used for as input number to the
* instruction and, as well as, to compute the RXB field of the
* instruction.
*/
.macro VX_NUM opd vxr
\opd = 255
.irp vs,0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31
.ifc \vxr,%v\vs
\opd = \vs
.endif
.endr
.if \opd == 255
\opd = \vxr
.endif
.endm
#endif /* __ASSEMBLER__ */
#endif /* __ASM_S390_INSN_COMMON_ASM_H */
Annotation
- Atlas domain: Architecture Layer / arch/s390.
- 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.