arch/parisc/include/uapi/asm/ioctl.h
Source file repositories/reference/linux-study-clean/arch/parisc/include/uapi/asm/ioctl.h
File Facts
- System
- Linux kernel
- Corpus path
arch/parisc/include/uapi/asm/ioctl.h- Extension
.h- Size
- 1710 bytes
- Lines
- 46
- Domain
- Architecture Layer
- Bucket
- arch/parisc
- 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-generic/ioctl.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef _ASM_PARISC_IOCTL_H
#define _ASM_PARISC_IOCTL_H
/* ioctl command encoding: 32 bits total, command in lower 16 bits,
* size of the parameter structure in the lower 14 bits of the
* upper 16 bits.
* Encoding the size of the parameter structure in the ioctl request
* is useful for catching programs compiled with old versions
* and to avoid overwriting user space outside the user buffer area.
* The highest 2 bits are reserved for indicating the ``access mode''.
* NOTE: This limits the max parameter size to 16kB -1 !
*/
/*
* Direction bits.
*/
#define _IOC_NONE 0U
#define _IOC_WRITE 2U
#define _IOC_READ 1U
#include <asm-generic/ioctl.h>
#endif /* _ASM_PARISC_IOCTL_H */
Annotation
- Immediate include surface: `asm-generic/ioctl.h`.
- Atlas domain: Architecture Layer / arch/parisc.
- 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.