drivers/gpu/tests/gpu_random.h
Source file repositories/reference/linux-study-clean/drivers/gpu/tests/gpu_random.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/tests/gpu_random.h- Extension
.h- Size
- 796 bytes
- Lines
- 29
- Domain
- Driver Families
- Bucket
- drivers/gpu
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/prandom.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef __GPU_RANDOM_H__
#define __GPU_RANDOM_H__
/* This is a temporary home for a couple of utility functions that should
* be transposed to lib/ at the earliest convenience.
*/
#include <linux/prandom.h>
#define GPU_RND_STATE_INITIALIZER(seed__) ({ \
struct rnd_state state__; \
prandom_seed_state(&state__, (seed__)); \
state__; \
})
#define GPU_RND_STATE(name__, seed__) \
struct rnd_state name__ = GPU_RND_STATE_INITIALIZER(seed__)
unsigned int *gpu_random_order(unsigned int count,
struct rnd_state *state);
void gpu_random_reorder(unsigned int *order,
unsigned int count,
struct rnd_state *state);
u32 gpu_prandom_u32_max_state(u32 ep_ro,
struct rnd_state *state);
#endif /* !__GPU_RANDOM_H__ */
Annotation
- Immediate include surface: `linux/prandom.h`.
- Atlas domain: Driver Families / drivers/gpu.
- 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.