linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: duchangbin <changbin.du@huawei.com>
To: duchangbin <changbin.du@huawei.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, "Ian Rogers" <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	"Liang, Kan" <kan.liang@linux.intel.com>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	"linux-perf-users@vger.kernel.org"
	<linux-perf-users@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
	"Wanghui (OS Kernel Lab, Beijing)" <hw.huiwang@huawei.com>
Subject: Re: [PATCH v5 0/8] perf: support specify vdso path in cmdline
Date: Mon, 15 Jul 2024 11:38:58 +0000	[thread overview]
Message-ID: <5b4a83c1a1614e23985a10e669d78eda@huawei.com> (raw)
In-Reply-To: <20240702041837.5306-1-changbin.du@huawei.com>

Hello, are there any more comments about this revision?

On Tue, Jul 02, 2024 at 12:18:29PM +0800, Changbin Du wrote:
> The vdso dumped from process memory (in buildid-cache) lacks debugging
> info. To annotate vdso symbols with source lines we need a debugging
> version.
> 
> For x86, we can find them from your local build as
> 'arch/x86/entry/vdso/vdso{32,64}.so.dbg'. Or they may resides in
> '/lib/modules/<version>/vdso/vdso{32,64}.so' on Ubuntu. But notice that the
> builid has to match. 
> 
> If user doesn't specify the path, perf will search them internally as long
> as vmlinux when recording samples. The searched debugging vdso will add to
> buildid cache.
> 
> Below samples are captured on my local build kernel. perf succesfully
> find debugging version vdso and we can annotate with source without
> specifying vdso path.
> 
> $ sudo perf record -a
> $ sudo perf report --objdump=llvm-objdump
> 
> Samples: 17K of event 'cycles:P', 4000 Hz, Event count (approx.): 1760
> __vdso_clock_gettime  /work/linux-host/arch/x86/entry/vdso/vdso64.so.d
> Percent│       movq    -48(%rbp),%rsi
>        │       testq   %rax,%rax
>        │     ;               return vread_hvclock();
>        │       movq    %rax,%rdx
>        │     ;               if (unlikely(!vdso_cycles_ok(cycles)))
>        │     ↑ js      eb
>        │     ↑ jmp     74
>        │     ;               ts->tv_sec = vdso_ts->sec;
>   0.02 │147:   leaq    2(%rbx),%rax
>        │       shlq    $4, %rax
>        │       addq    %r10,%rax
>        │     ;               while ((seq = READ_ONCE(vd->seq)) & 1) {
>   9.38 │152:   movl    (%r10),%ecx
> 
> When doing cross platform analysis, we need to specify the vdso path if
> we are interested in its symbols. At most two vdso can be given. Also you
> can pack your buildid cache with perf-archive if the debugging vdso can be
> found on the sampled machine.
> 
> $ sudo perf report --objdump=llvm-objdump \
>       --vdso arch/x86/entry/vdso/vdso64.so.dbg,arch/x86/entry/vdso/vdso32.so.dbg
> 
> I also improved perf-buildid-cache command recognize vdso when adding files, then
> place it at correct place.
> 
> v5:
>   - Searching the vdso in record stage instead of report. So the debugging
>     vdso will be in build-id cache. This is friendly for cross-machine analysis.
>   - Improve perf-buildid-cache command recognize vdso when adding files
> v4:
>   - split the refactoring from the actual change.
> v3:
>   - update documentation.
> v2:
>   - now search vdso automatically as long as vmlinux, as suggested by Adrian.
>   - remove change 'prefer symsrc_filename for filename'.
> 
> 
> Changbin Du (8):
>   perf: support specify vdso path in cmdline
>   perf: disasm: refactor function dso__disassemble_filename
>   perf: disasm: use build_id_path if fallback failed
>   perf: build-id: name debugging vdso as "debug"
>   perf: symbol: generalize vmlinux path searching
>   perf: build-id: try to search debugging vdso and add to cache
>   perf: disasm: prefer debugging files in build-id cache
>   perf buildid-cache: recognize vdso when adding files
> 
>  tools/perf/Documentation/perf-annotate.txt |   3 +
>  tools/perf/Documentation/perf-c2c.txt      |   3 +
>  tools/perf/Documentation/perf-inject.txt   |   3 +
>  tools/perf/Documentation/perf-report.txt   |   3 +
>  tools/perf/Documentation/perf-script.txt   |   3 +
>  tools/perf/Documentation/perf-top.txt      |   3 +
>  tools/perf/builtin-annotate.c              |   2 +
>  tools/perf/builtin-buildid-cache.c         |  26 ++-
>  tools/perf/builtin-c2c.c                   |   2 +
>  tools/perf/builtin-inject.c                |   2 +
>  tools/perf/builtin-report.c                |   2 +
>  tools/perf/builtin-script.c                |   2 +
>  tools/perf/builtin-top.c                   |   2 +
>  tools/perf/util/build-id.c                 |  57 +++++-
>  tools/perf/util/disasm.c                   | 131 ++++++++-----
>  tools/perf/util/machine.c                  |   4 +-
>  tools/perf/util/symbol.c                   | 209 ++++++++++++++++-----
>  tools/perf/util/symbol.h                   |   9 +-
>  tools/perf/util/symbol_conf.h              |   5 +
>  19 files changed, 359 insertions(+), 112 deletions(-)
> 
> -- 
> 2.34.1
> 

-- 
Cheers,
Changbin Du

      parent reply	other threads:[~2024-07-15 11:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02  4:18 [PATCH v5 0/8] perf: support specify vdso path in cmdline Changbin Du
2024-07-02  4:18 ` [PATCH v5 1/8] " Changbin Du
2024-07-18 17:02   ` Adrian Hunter
2024-07-22 12:19     ` duchangbin
2024-07-22 13:15       ` Adrian Hunter
2024-07-23  1:50         ` duchangbin
2024-07-02  4:18 ` [PATCH v5 2/8] perf: disasm: refactor function dso__disassemble_filename Changbin Du
2024-07-02  4:18 ` [PATCH v5 3/8] perf: disasm: use build_id_path if fallback failed Changbin Du
2024-07-02  4:18 ` [PATCH v5 4/8] perf: build-id: name debugging vdso as "debug" Changbin Du
2024-07-18 17:03   ` Adrian Hunter
2024-07-22 12:08     ` duchangbin
2024-07-22 13:21       ` Adrian Hunter
2024-07-23  1:51         ` duchangbin
2024-07-02  4:18 ` [PATCH v5 5/8] perf: symbol: generalize vmlinux path searching Changbin Du
2024-07-02  4:18 ` [PATCH v5 6/8] perf: build-id: try to search debugging vdso and add to cache Changbin Du
2024-07-02  4:18 ` [PATCH v5 7/8] perf: disasm: prefer debugging files in build-id cache Changbin Du
2024-07-02  4:18 ` [PATCH v5 8/8] perf buildid-cache: recognize vdso when adding files Changbin Du
2024-07-03 23:18   ` Namhyung Kim
2024-07-04  1:43     ` duchangbin
2024-07-24 14:55   ` kernel test robot
2024-07-15 11:38 ` duchangbin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5b4a83c1a1614e23985a10e669d78eda@huawei.com \
    --to=changbin.du@huawei.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=hw.huiwang@huawei.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=justinstitt@google.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=morbo@google.com \
    --cc=namhyung@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).