tools/perf/util/bpf_skel/syscall_summary.h
Source file repositories/reference/linux-study-clean/tools/perf/util/bpf_skel/syscall_summary.h
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/util/bpf_skel/syscall_summary.h- Extension
.h- Size
- 509 bytes
- Lines
- 28
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
struct syscall_keystruct syscall_statsenum syscall_aggr_mode
Annotated Snippet
struct syscall_key {
u64 cgroup;
int cpu_or_tid;
int nr;
};
struct syscall_stats {
u64 total_time;
u64 squared_sum;
u64 max_time;
u64 min_time;
u32 count;
u32 error;
};
#endif /* UTIL_BPF_SKEL_SYSCALL_SUMMARY_H */
Annotation
- Detected declarations: `struct syscall_key`, `struct syscall_stats`, `enum syscall_aggr_mode`.
- 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.