1perf-inject(1)
 2==============
 3
 4NAME
 5----
 6perf-inject - Filter to augment the events stream with additional information
 7
 8SYNOPSIS
 9--------
10[verse]
11'perf inject <options>'
12
13DESCRIPTION
14-----------
15perf-inject reads a perf-record event stream and repipes it to stdout.  At any
16point the processing code can inject other events into the event stream - in
17this case build-ids (-b option) are read and injected as needed into the event
18stream.
19
20Build-ids are just the first user of perf-inject - potentially anything that
21needs userspace processing to augment the events stream with additional
22information could make use of this facility.
23
24OPTIONS
25-------
26-b::
27--build-ids::
28        Inject build-ids into the output stream
29
30--buildid-all:
31	Inject build-ids of all DSOs into the output stream
32
33-v::
34--verbose::
35	Be more verbose.
36-i::
37--input=::
38	Input file name. (default: stdin)
39-o::
40--output=::
41	Output file name. (default: stdout)
42-s::
43--sched-stat::
44	Merge sched_stat and sched_switch for getting events where and how long
45	tasks slept. sched_switch contains a callchain where a task slept and
46	sched_stat contains a timeslice how long a task slept.
47
48--kallsyms=<file>::
49	kallsyms pathname
50
51--itrace::
52	Decode Instruction Tracing data, replacing it with synthesized events.
53	Options are:
54
55include::itrace.txt[]
56
57--strip::
58	Use with --itrace to strip out non-synthesized events.
59
60-j::
61--jit::
62	Process jitdump files by injecting the mmap records corresponding to jitted
63	functions. This option also generates the ELF images for each jitted function
64	found in the jitdumps files captured in the input perf.data file. Use this option
65	if you are monitoring environment using JIT runtimes, such as Java, DART or V8.
66
67-f::
68--force::
69	Don't complain, do it.
70
71--vm-time-correlation[=OPTIONS]::
72	Some architectures may capture AUX area data which contains timestamps
73	affected by virtualization. This option will update those timestamps
74	in place, to correlate with host timestamps. The in-place update means
75	that an output file is not specified, and instead the input file is
76	modified.  The options are architecture specific, except that they may
77	start with "dry-run" which will cause the file to be processed but
78	without updating it. Currently this option is supported only by
79	Intel PT, refer linkperf:perf-intel-pt[1]
80
81SEE ALSO
82--------
83linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-archive[1],
84linkperf:perf-intel-pt[1]

 1perf-inject(1)
 2==============
 3
 4NAME
 5----
 6perf-inject - Filter to augment the events stream with additional information
 7
 8SYNOPSIS
 9--------
10[verse]
11'perf inject <options>'
12
13DESCRIPTION
14-----------
15perf-inject reads a perf-record event stream and repipes it to stdout.  At any
16point the processing code can inject other events into the event stream - in
17this case build-ids (-b option) are read and injected as needed into the event
18stream.
19
20Build-ids are just the first user of perf-inject - potentially anything that
21needs userspace processing to augment the events stream with additional
22information could make use of this facility.
23
24OPTIONS
25-------
26-b::
27--build-ids=::
28        Inject build-ids into the output stream
 
 
 
 
29-v::
30--verbose::
31	Be more verbose.
32-i::
33--input=::
34	Input file name. (default: stdin)
35-o::
36--output=::
37	Output file name. (default: stdout)
38-s::
39--sched-stat::
40	Merge sched_stat and sched_switch for getting events where and how long
41	tasks slept. sched_switch contains a callchain where a task slept and
42	sched_stat contains a timeslice how long a task slept.
43
44--kallsyms=<file>::
45	kallsyms pathname
46
47--itrace::
48	Decode Instruction Tracing data, replacing it with synthesized events.
49	Options are:
50
51include::itrace.txt[]
52
53--strip::
54	Use with --itrace to strip out non-synthesized events.
55
56-j::
57--jit::
58	Process jitdump files by injecting the mmap records corresponding to jitted
59	functions. This option also generates the ELF images for each jitted function
60	found in the jitdumps files captured in the input perf.data file. Use this option
61	if you are monitoring environment using JIT runtimes, such as Java, DART or V8.
62
63-f::
64--force::
65	Don't complain, do it.
66
 
 
 
 
 
 
 
 
 
 
67SEE ALSO
68--------
69linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-archive[1]