1PERF-BUILDID-CACHE(1)             perf Manual            PERF-BUILDID-CACHE(1)
2
3
4

NAME

6       perf-buildid-cache - Manage build-id cache.
7

SYNOPSIS

9       perf buildid-cache <options>
10

DESCRIPTION

12       This command manages the build-id cache. It can add, remove, update and
13       purge files to/from the cache. In the future it should as well set
14       upper limits for the space used by the cache, etc. This also scans the
15       target binary for SDT (Statically Defined Tracing) and record it along
16       with the buildid-cache, which will be used by perf-probe. For more
17       details, see perf-probe(1).
18

OPTIONS

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

SEE ALSO

59       perf-record(1), perf-report(1), perf-buildid-list(1)
60
61
62
63perf                              06/18/2019             PERF-BUILDID-CACHE(1)
Impressum