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

 1perf-buildid-cache(1)
 2=====================
 3
 4NAME
 5----
 6perf-buildid-cache - Manage build-id cache.
 7
 8SYNOPSIS
 9--------
10[verse]
11'perf buildid-cache <options>'
12
13DESCRIPTION
14-----------
15This command manages the build-id cache. It can add and remove files to/from
16the cache. In the future it should as well purge older entries, set upper
17limits for the space used by the cache, etc.
 
 
 
18
19OPTIONS
20-------
21-a::
22--add=::
23        Add specified file to the cache.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
24-r::
25--remove=::
26        Remove specified file from the cache.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
27-v::
28--verbose::
29	Be more verbose.
 
 
 
 
 
30
31SEE ALSO
32--------
33linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-buildid-list[1]