This command manages the build-id cache. It can add, remove, update
and purge files to/from the cache. In the future it should as well
set upper limits for the space used by the cache, etc. This also
scans the target binary for SDT (Statically Defined Tracing) and
record it along with the buildid-cache, which will be used by
perf-probe. For more details, see perf-probe(1).
Add specified file to the cache.
Add specified kcore file to the cache. For the current host that
is /proc/kcore which requires root permissions to read. Be aware
that running perf buildid-cache as root may update root’s
build-id cache not the user’s. Use the -v option to see where the
file is created. Note that the copied file contains only code
sections not the whole core image. Note also that files
"kallsyms" and "modules" must also be in the same directory and
are also copied. All 3 files are created with read permissions
for root only. kcore will not be added if there is already a
kcore in the cache (with the same build-id) that has the same
modules at the same addresses. Use the -v option to see if a copy
of kcore is actually made.
Remove a cached binary which has same build-id of specified file
from the cache.
Purge all cached binaries including older caches which have
specified path from the cache.
List missing build ids in the cache for the specified file.
Update specified file of the cache. Note that this doesn’t remove
older entires since those may be still needed for annotating old
(or remote) perf.data. Only if there is already a cache which has
exactly same build-id, that is replaced by new one. It can be
used to update kallsyms and kernel dso to vmlinux in order to
Be more verbose.
This page is part of the perf (Performance analysis tools for Linux
(in Linux source tree)) project. Information about the project can
be found at ⟨https://perf.wiki.kernel.org/index.php/Main_Page⟩. If
you have a bug report for this manual page, send it to
firstname.lastname@example.org. This page was obtained from the
project's upstream Git repository
2017-03-13. If you discover any rendering problems in this HTML ver‐
sion of the page, or you believe there is a better or more up-to-date
source for the page, or you have corrections or improvements to the
information in this COLOPHON (which is not part of the original man‐
ual page), send a mail to email@example.com
perf 02/18/2017 PERF-BUILDID-CACHE(1)