tools/perf/util/threads.h
Source file repositories/reference/linux-study-clean/tools/perf/util/threads.h
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/util/threads.h- Extension
.h- Size
- 1066 bytes
- Lines
- 36
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
hashmap.hrwsem.h
Detected Declarations
struct threadstruct threads_table_entrystruct threads
Annotated Snippet
struct threads_table_entry {
/* Key is tid, value is struct thread. */
struct hashmap shard;
struct rw_semaphore lock;
struct thread *last_match;
};
struct threads {
struct threads_table_entry table[THREADS__TABLE_SIZE];
};
void threads__init(struct threads *threads);
void threads__exit(struct threads *threads);
size_t threads__nr(struct threads *threads);
struct thread *threads__find(struct threads *threads, pid_t tid);
struct thread *threads__findnew(struct threads *threads, pid_t pid, pid_t tid, bool *created);
void threads__remove_all_threads(struct threads *threads);
void threads__remove(struct threads *threads, struct thread *thread);
int threads__for_each_thread(struct threads *threads,
int (*fn)(struct thread *thread, void *data),
void *data);
#endif /* __PERF_THREADS_H */
Annotation
- Immediate include surface: `hashmap.h`, `rwsem.h`.
- Detected declarations: `struct thread`, `struct threads_table_entry`, `struct threads`.
- 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.