perf-inject.txt 1.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576
  1. perf-inject(1)
  2. ==============
  3. NAME
  4. ----
  5. perf-inject - Filter to augment the events stream with additional information
  6. SYNOPSIS
  7. --------
  8. [verse]
  9. 'perf inject <options>'
  10. DESCRIPTION
  11. -----------
  12. perf-inject reads a perf-record event stream and repipes it to stdout. At any
  13. point the processing code can inject other events into the event stream - in
  14. this case build-ids (-b option) are read and injected as needed into the event
  15. stream.
  16. Build-ids are just the first user of perf-inject - potentially anything that
  17. needs userspace processing to augment the events stream with additional
  18. information could make use of this facility.
  19. OPTIONS
  20. -------
  21. -b::
  22. --build-ids=::
  23. Inject build-ids into the output stream
  24. -v::
  25. --verbose::
  26. Be more verbose.
  27. -i::
  28. --input=::
  29. Input file name. (default: stdin)
  30. -o::
  31. --output=::
  32. Output file name. (default: stdout)
  33. -s::
  34. --sched-stat::
  35. Merge sched_stat and sched_switch for getting events where and how long
  36. tasks slept. sched_switch contains a callchain where a task slept and
  37. sched_stat contains a timeslice how long a task slept.
  38. --kallsyms=<file>::
  39. kallsyms pathname
  40. --itrace::
  41. Decode Instruction Tracing data, replacing it with synthesized events.
  42. Options are:
  43. i synthesize instructions events
  44. b synthesize branches events
  45. c synthesize branches events (calls only)
  46. r synthesize branches events (returns only)
  47. x synthesize transactions events
  48. e synthesize error events
  49. d create a debug log
  50. g synthesize a call chain (use with i or x)
  51. The default is all events i.e. the same as --itrace=ibxe
  52. In addition, the period (default 100000) for instructions events
  53. can be specified in units of:
  54. i instructions
  55. t ticks
  56. ms milliseconds
  57. us microseconds
  58. ns nanoseconds (default)
  59. Also the call chain size (default 16, max. 1024) for instructions or
  60. transactions events can be specified.
  61. SEE ALSO
  62. --------
  63. linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-archive[1]