perf-buildid-cache.txt 2.6 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980
  1. perf-buildid-cache(1)
  2. =====================
  3. NAME
  4. ----
  5. perf-buildid-cache - Manage build-id cache.
  6. SYNOPSIS
  7. --------
  8. [verse]
  9. 'perf buildid-cache <options>'
  10. DESCRIPTION
  11. -----------
  12. This command manages the build-id cache. It can add, remove, update and purge
  13. files to/from the cache. In the future it should as well set upper limits for
  14. the space used by the cache, etc.
  15. This also scans the target binary for SDT (Statically Defined Tracing) and
  16. record it along with the buildid-cache, which will be used by perf-probe.
  17. For more details, see linkperf:perf-probe[1].
  18. OPTIONS
  19. -------
  20. -a::
  21. --add=::
  22. Add specified file to the cache.
  23. -f::
  24. --force::
  25. Don't complain, do it.
  26. -k::
  27. --kcore::
  28. Add specified kcore file to the cache. For the current host that is
  29. /proc/kcore which requires root permissions to read. Be aware that
  30. running 'perf buildid-cache' as root may update root's build-id cache
  31. not the user's. Use the -v option to see where the file is created.
  32. Note that the copied file contains only code sections not the whole core
  33. image. Note also that files "kallsyms" and "modules" must also be in the
  34. same directory and are also copied. All 3 files are created with read
  35. permissions for root only. kcore will not be added if there is already a
  36. kcore in the cache (with the same build-id) that has the same modules at
  37. the same addresses. Use the -v option to see if a copy of kcore is
  38. actually made.
  39. -r::
  40. --remove=::
  41. Remove a cached binary which has same build-id of specified file
  42. from the cache.
  43. -p::
  44. --purge=::
  45. Purge all cached binaries including older caches which have specified
  46. path from the cache.
  47. -P::
  48. --purge-all::
  49. Purge all cached binaries. This will flush out entire cache.
  50. -M::
  51. --missing=::
  52. List missing build ids in the cache for the specified file.
  53. -u::
  54. --update=::
  55. Update specified file of the cache. Note that this doesn't remove
  56. older entires since those may be still needed for annotating old
  57. (or remote) perf.data. Only if there is already a cache which has
  58. exactly same build-id, that is replaced by new one. It can be used
  59. to update kallsyms and kernel dso to vmlinux in order to support
  60. annotation.
  61. -l::
  62. --list::
  63. List all valid binaries from cache.
  64. -v::
  65. --verbose::
  66. Be more verbose.
  67. --target-ns=PID:
  68. Obtain mount namespace information from the target pid. This is
  69. used when creating a uprobe for a process that resides in a
  70. different mount namespace from the perf(1) utility.
  71. SEE ALSO
  72. --------
  73. linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-buildid-list[1]