diff options
| author | Changbin Du <changbin.du@huawei.com> | 2026-03-09 17:44:12 +0000 |
|---|---|---|
| committer | Namhyung Kim <namhyung@kernel.org> | 2026-03-10 23:13:30 -0700 |
| commit | f182573e06abb635f320b0fd0e60972c4c2467c5 (patch) | |
| tree | d5c1ea33d3b9d933b84e5026150a577774d5d14e /tools/perf/Documentation/tips.txt | |
| parent | 86ff690f45cc034ab32246630b3c7d7a46d1ae6b (diff) | |
| download | linux-next-f182573e06abb635f320b0fd0e60972c4c2467c5.tar.gz linux-next-f182573e06abb635f320b0fd0e60972c4c2467c5.zip | |
perf tools: Add layout support for --symfs option
Add support for parsing an optional layout parameter in the --symfs
command line option. The format is:
--symfs <directory[,layout]>
Where layout can be:
- 'hierarchy': matches full path (default)
- 'flat': only matches base name
When debugging symbol files from a copy of the filesystem (e.g., from a
container or remote machine), the debug files are often stored in a
flat directory structure with only filenames, not the full original
paths. In this case, using 'flat' layout allows perf to find debug
symbols by matching only the filename rather than the full path.
For example, given a binary path like:
/build/output/lib/foo.so
With 'perf report --symfs /debug/files,flat', perf will look for:
/debug/files/foo.so
Instead of:
/debug/files/build/output/lib/foo.so
This is particularly useful when:
- Extracting debug files from containers with different directory layouts
- Working with build systems that flatten directory structures
Signed-off-by: Changbin Du <changbin.du@huawei.com>
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Diffstat (limited to 'tools/perf/Documentation/tips.txt')
| -rw-r--r-- | tools/perf/Documentation/tips.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/perf/Documentation/tips.txt b/tools/perf/Documentation/tips.txt index 3fee9b2a88ea..ebf12a8c5db5 100644 --- a/tools/perf/Documentation/tips.txt +++ b/tools/perf/Documentation/tips.txt @@ -11,7 +11,7 @@ Search options using a keyword: perf report -h <keyword> Use parent filter to see specific call path: perf report -p <regex> List events using substring match: perf list <keyword> To see list of saved events and attributes: perf evlist -v -Use --symfs <dir> if your symbol files are in non-standard locations +Use --symfs <dir>[,layout] if your symbol files are in non-standard locations. To see callchains in a more compact form: perf report -g folded To see call chains by final symbol taking CPU time (bottom up) use perf report -G Show individual samples with: perf script |
