tools/testing/selftests/powerpc/syscalls/ipc.h
Source file repositories/reference/linux-study-clean/tools/testing/selftests/powerpc/syscalls/ipc.h
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/powerpc/syscalls/ipc.h- Extension
.h- Size
- 713 bytes
- Lines
- 49
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: syscall or user/kernel boundary
- Status
- core implementation candidate
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Defines or participates in a user/kernel boundary; inspect argument validation, copy_from_user/copy_to_user, credentials, and dispatch target.
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
#ifdef __NR_semop
DO_TEST(semop, __NR_semop)
#endif
#ifdef __NR_semget
DO_TEST(semget, __NR_semget)
#endif
#ifdef __NR_semctl
DO_TEST(semctl, __NR_semctl)
#endif
#ifdef __NR_semtimedop
DO_TEST(semtimedop, __NR_semtimedop)
#endif
#ifdef __NR_msgsnd
DO_TEST(msgsnd, __NR_msgsnd)
#endif
#ifdef __NR_msgrcv
DO_TEST(msgrcv, __NR_msgrcv)
#endif
#ifdef __NR_msgget
DO_TEST(msgget, __NR_msgget)
#endif
#ifdef __NR_msgctl
DO_TEST(msgctl, __NR_msgctl)
#endif
#ifdef __NR_shmat
DO_TEST(shmat, __NR_shmat)
#endif
#ifdef __NR_shmdt
DO_TEST(shmdt, __NR_shmdt)
#endif
#ifdef __NR_shmget
DO_TEST(shmget, __NR_shmget)
#endif
#ifdef __NR_shmctl
DO_TEST(shmctl, __NR_shmctl)
#endif
Annotation
- Atlas domain: Support Tooling And Documentation / tools.
- Implementation status: core 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.