perf-buildid-cache.txt 2.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667
  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. -k::
  24. --kcore::
  25. Add specified kcore file to the cache. For the current host that is
  26. /proc/kcore which requires root permissions to read. Be aware that
  27. running 'perf buildid-cache' as root may update root's build-id cache
  28. not the user's. Use the -v option to see where the file is created.
  29. Note that the copied file contains only code sections not the whole core
  30. image. Note also that files "kallsyms" and "modules" must also be in the
  31. same directory and are also copied. All 3 files are created with read
  32. permissions for root only. kcore will not be added if there is already a
  33. kcore in the cache (with the same build-id) that has the same modules at
  34. the same addresses. Use the -v option to see if a copy of kcore is
  35. actually made.
  36. -r::
  37. --remove=::
  38. Remove a cached binary which has same build-id of specified file
  39. from the cache.
  40. -p::
  41. --purge=::
  42. Purge all cached binaries including older caches which have specified
  43. path from the cache.
  44. -M::
  45. --missing=::
  46. List missing build ids in the cache for the specified file.
  47. -u::
  48. --update=::
  49. Update specified file of the cache. Note that this doesn't remove
  50. older entires since those may be still needed for annotating old
  51. (or remote) perf.data. Only if there is already a cache which has
  52. exactly same build-id, that is replaced by new one. It can be used
  53. to update kallsyms and kernel dso to vmlinux in order to support
  54. annotation.
  55. -v::
  56. --verbose::
  57. Be more verbose.
  58. SEE ALSO
  59. --------
  60. linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-buildid-list[1]