tools/testing/selftests/rseq/rseq-thread-pointer.h

Source file repositories/reference/linux-study-clean/tools/testing/selftests/rseq/rseq-thread-pointer.h

File Facts

System: Linux kernel
Corpus path: tools/testing/selftests/rseq/rseq-thread-pointer.h
Extension: .h
Size: 488 bytes
Lines: 22
Domain: Support Tooling And Documentation
Bucket: tools
Inferred role: Support Tooling And Documentation: implementation source
Status: source 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.

Dependency Surface

rseq-x86-thread-pointer.h
rseq-ppc-thread-pointer.h
rseq-or1k-thread-pointer.h
rseq-generic-thread-pointer.h

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef _RSEQ_THREAD_POINTER
#define _RSEQ_THREAD_POINTER

#if defined(__x86_64__) || defined(__i386__)
#include "rseq-x86-thread-pointer.h"
#elif defined(__PPC__)
#include "rseq-ppc-thread-pointer.h"
#elif defined(__or1k__)
#include "rseq-or1k-thread-pointer.h"
#else
#include "rseq-generic-thread-pointer.h"
#endif

#endif

Annotation

Immediate include surface: `rseq-x86-thread-pointer.h`, `rseq-ppc-thread-pointer.h`, `rseq-or1k-thread-pointer.h`, `rseq-generic-thread-pointer.h`.
Atlas domain: Support Tooling And Documentation / tools.
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.