tools/perf/Documentation/perf-inject.txt
Source file repositories/reference/linux-study-clean/tools/perf/Documentation/perf-inject.txt
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/Documentation/perf-inject.txt- Extension
.txt- Size
- 4126 bytes
- Lines
- 125
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: documentation
- Status
- atlas-only
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
- 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
Currently only mmap, mmap2, comm, task, context_switch, ksymbol,
and text_poke events are inserted, as well as build ID information.
The QEMU option -name debug-threads=on is needed so that thread names
can be used to determine which thread is running which VCPU. Note
libvirt seems to use this by default.
When using perf record in the guest, option --sample-identifier
should be used, and also --buildid-all and --switch-events may be
useful.
--convert-callchain::
Parse DWARF callchains and convert them to usual callchains. This also
discards stack and register data from the samples. This will lose
inlined callchain entries.
:GMEXAMPLECMD: inject
:GMEXAMPLESUBCMD:
include::guestmount.txt[]
SEE ALSO
--------
linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-archive[1],
linkperf:perf-intel-pt[1]
Annotation
- Atlas domain: Support Tooling And Documentation / tools.
- Implementation status: atlas-only.
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.