From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: He Kuang <hekuang@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
wangnan0@huawei.com, jpoimboe@redhat.com, ak@linux.intel.com,
eranian@google.com, namhyung@kernel.org, adrian.hunter@intel.com,
sukadev@linux.vnet.ibm.com, masami.hiramatsu.pt@hitachi.com,
tumanova@linux.vnet.ibm.com, kan.liang@intel.com,
penberg@kernel.org, dsahern@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/8] perf script: Add options for custom vdso name
Date: Fri, 6 May 2016 08:49:39 -0300 [thread overview]
Message-ID: <20160506114939.GU11069@kernel.org> (raw)
In-Reply-To: <1462525154-125656-3-git-send-email-hekuang@huawei.com>
Em Fri, May 06, 2016 at 08:59:08AM +0000, He Kuang escreveu:
> When unwinding callchain on different machine, vdso info should be
> provided so the unwind process won't be interrupted if address fell
> into vdso region.
>
> Signed-off-by: He Kuang <hekuang@huawei.com>
> ---
> tools/perf/builtin-script.c | 2 ++
> tools/perf/util/dso.c | 7 +++++++
> tools/perf/util/dso.h | 1 +
> tools/perf/util/symbol.c | 1 +
> tools/perf/util/symbol.h | 1 +
> 5 files changed, 12 insertions(+)
>
> diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
> index 8f6ab2a..c88b547 100644
> --- a/tools/perf/builtin-script.c
> +++ b/tools/perf/builtin-script.c
> @@ -2001,6 +2001,8 @@ int cmd_script(int argc, const char **argv, const char *prefix __maybe_unused)
> "file", "vmlinux pathname"),
> OPT_STRING(0, "kallsyms", &symbol_conf.kallsyms_name,
> "file", "kallsyms pathname"),
> + OPT_STRING(0, "vdso", &symbol_conf.vdso_name,
> + "file", "vdso pathname"),
> OPT_BOOLEAN('G', "hide-call-graph", &no_callchain,
> "When printing symbols do not display call chain"),
> OPT_STRING(0, "symfs", &symbol_conf.symfs, "directory",
> diff --git a/tools/perf/util/dso.c b/tools/perf/util/dso.c
> index 8e639543..344db10 100644
> --- a/tools/perf/util/dso.c
> +++ b/tools/perf/util/dso.c
> @@ -21,6 +21,7 @@ char dso__symtab_origin(const struct dso *dso)
> [DSO_BINARY_TYPE__OPENEMBEDDED_DEBUGINFO] = 'o',
> [DSO_BINARY_TYPE__BUILDID_DEBUGINFO] = 'b',
> [DSO_BINARY_TYPE__SYSTEM_PATH_DSO] = 'd',
> + [DSO_BINARY_TYPE__SYSTEM_PATH_DSO_CUSTOM] = 'r',
> [DSO_BINARY_TYPE__SYSTEM_PATH_KMODULE] = 'K',
> [DSO_BINARY_TYPE__SYSTEM_PATH_KMODULE_COMP] = 'm',
> [DSO_BINARY_TYPE__GUEST_KALLSYMS] = 'g',
> @@ -113,6 +114,11 @@ int dso__read_binary_type_filename(const struct dso *dso,
> build_id_hex, build_id_hex + 2);
> break;
>
> + case DSO_BINARY_TYPE__SYSTEM_PATH_DSO_CUSTOM:
> + {
> + snprintf(filename, size, "%s", symbol_conf.vdso_name);
> + break;
> + }
Remove the {}, not needed at all.
> case DSO_BINARY_TYPE__VMLINUX:
> case DSO_BINARY_TYPE__GUEST_VMLINUX:
> case DSO_BINARY_TYPE__SYSTEM_PATH_DSO:
> @@ -487,6 +493,7 @@ static void try_to_open_dso(struct dso *dso, struct machine *machine)
> enum dso_binary_type binary_type_data[] = {
> DSO_BINARY_TYPE__BUILD_ID_CACHE,
> DSO_BINARY_TYPE__SYSTEM_PATH_DSO,
> + DSO_BINARY_TYPE__SYSTEM_PATH_DSO_CUSTOM,
Why do you call it a "DSO_CUSTOM" in some places while in others you
call it vdso_name?
> DSO_BINARY_TYPE__NOT_FOUND,
> };
> int i = 0;
> diff --git a/tools/perf/util/dso.h b/tools/perf/util/dso.h
> index 0953280..f55ce5b 100644
> --- a/tools/perf/util/dso.h
> +++ b/tools/perf/util/dso.h
> @@ -23,6 +23,7 @@ enum dso_binary_type {
> DSO_BINARY_TYPE__UBUNTU_DEBUGINFO,
> DSO_BINARY_TYPE__BUILDID_DEBUGINFO,
> DSO_BINARY_TYPE__SYSTEM_PATH_DSO,
> + DSO_BINARY_TYPE__SYSTEM_PATH_DSO_CUSTOM,
> DSO_BINARY_TYPE__GUEST_KMODULE,
> DSO_BINARY_TYPE__GUEST_KMODULE_COMP,
> DSO_BINARY_TYPE__SYSTEM_PATH_KMODULE,
> diff --git a/tools/perf/util/symbol.c b/tools/perf/util/symbol.c
> index e7588dc..93f348f 100644
> --- a/tools/perf/util/symbol.c
> +++ b/tools/perf/util/symbol.c
> @@ -1359,6 +1359,7 @@ static bool dso__is_compatible_symtab_type(struct dso *dso, bool kmod,
> case DSO_BINARY_TYPE__JAVA_JIT:
> case DSO_BINARY_TYPE__DEBUGLINK:
> case DSO_BINARY_TYPE__SYSTEM_PATH_DSO:
> + case DSO_BINARY_TYPE__SYSTEM_PATH_DSO_CUSTOM:
> case DSO_BINARY_TYPE__FEDORA_DEBUGINFO:
> case DSO_BINARY_TYPE__UBUNTU_DEBUGINFO:
> case DSO_BINARY_TYPE__BUILDID_DEBUGINFO:
> diff --git a/tools/perf/util/symbol.h b/tools/perf/util/symbol.h
> index c8b7544..4e6910e 100644
> --- a/tools/perf/util/symbol.h
> +++ b/tools/perf/util/symbol.h
> @@ -114,6 +114,7 @@ struct symbol_conf {
> report_hierarchy;
> const char *vmlinux_name,
> *kallsyms_name,
> + *vdso_name,
> *source_prefix,
> *field_sep;
> const char *default_guest_vmlinux_name,
> --
> 1.8.5.2
next prev parent reply other threads:[~2016-05-06 11:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 8:59 [PATCH 0/8] Add support for remote unwind He Kuang
2016-05-06 8:59 ` [PATCH 1/8] perf tools: Omit DWARF judgement when recording dwarf callchain He Kuang
2016-05-06 11:47 ` Arnaldo Carvalho de Melo
2016-05-07 18:03 ` Jiri Olsa
2016-05-09 16:16 ` Arnaldo Carvalho de Melo
2016-05-10 1:44 ` Hekuang
2016-05-10 20:30 ` [tip:perf/core] perf callchain: Recording 'dwarf' callchains do not need DWARF unwinding support tip-bot for He Kuang
2016-05-06 8:59 ` [PATCH 2/8] perf script: Add options for custom vdso name He Kuang
2016-05-06 11:49 ` Arnaldo Carvalho de Melo [this message]
2016-05-07 18:14 ` Jiri Olsa
2016-05-06 8:59 ` [PATCH 3/8] perf build: Add build-test for libunwind cross-platforms support He Kuang
2016-05-07 18:20 ` Jiri Olsa
2016-05-06 8:59 ` [PATCH 4/8] perf build: Add build-test for debug-frame on arm/arm64 He Kuang
2016-05-07 18:24 ` Jiri Olsa
2016-05-06 8:59 ` [PATCH 5/8] perf tools: Promote proper messages for cross-platform unwind He Kuang
2016-05-07 18:41 ` Jiri Olsa
2016-05-07 18:42 ` Jiri Olsa
2016-05-06 8:59 ` [PATCH 6/8] perf callchain: Add support " He Kuang
2016-05-06 11:56 ` Arnaldo Carvalho de Melo
2016-05-06 8:59 ` [PATCH 7/8] perf callchain: Support x86 target platform He Kuang
2016-05-06 8:59 ` [PATCH 8/8] perf callchain: Support aarch64 cross-platform He Kuang
2016-05-06 11:58 ` [PATCH 0/8] Add support for remote unwind Arnaldo Carvalho de Melo
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=20160506114939.GU11069@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=hekuang@huawei.com \
--cc=jolsa@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
--cc=sukadev@linux.vnet.ibm.com \
--cc=tumanova@linux.vnet.ibm.com \
--cc=wangnan0@huawei.com \
/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).