arch/parisc/include/uapi/asm/ipcbuf.h
Source file repositories/reference/linux-study-clean/arch/parisc/include/uapi/asm/ipcbuf.h
File Facts
- System
- Linux kernel
- Corpus path
arch/parisc/include/uapi/asm/ipcbuf.h- Extension
.h- Size
- 837 bytes
- Lines
- 34
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
asm/bitsperlong.hlinux/posix_types.h
Detected Declarations
struct ipc64_perm
Annotated Snippet
#ifndef __PARISC_IPCBUF_H__
#define __PARISC_IPCBUF_H__
#include <asm/bitsperlong.h>
#include <linux/posix_types.h>
/*
* The ipc64_perm structure for PA-RISC is almost identical to
* kern_ipc_perm as we have always had 32-bit UIDs and GIDs in the kernel.
* 'seq' has been changed from long to int so that it's the same size
* on 64-bit kernels as on 32-bit ones.
*/
struct ipc64_perm
{
__kernel_key_t key;
__kernel_uid_t uid;
__kernel_gid_t gid;
__kernel_uid_t cuid;
__kernel_gid_t cgid;
#if __BITS_PER_LONG != 64
unsigned short int __pad1;
#endif
__kernel_mode_t mode;
unsigned short int __pad2;
unsigned short int seq;
unsigned int __pad3;
unsigned long long int __unused1;
unsigned long long int __unused2;
};
#endif /* __PARISC_IPCBUF_H__ */
Annotation
- Immediate include surface: `asm/bitsperlong.h`, `linux/posix_types.h`.
- Detected declarations: `struct ipc64_perm`.
- 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.