linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: He Kuang <hekuang@huawei.com>,
	peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	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
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/6] perf tools: Set buildid dir under symfs when --symfs is provided
Date: Thu, 19 May 2016 08:23:06 -0600	[thread overview]
Message-ID: <10081742-ebd5-fa1c-3531-b0afe510d16d@gmail.com> (raw)
In-Reply-To: <1463658462-85131-2-git-send-email-hekuang@huawei.com>

On 5/19/16 5:47 AM, He Kuang wrote:
> This patch moves the reference of buildid dir to 'symfs/.debug' and
> skips the local buildid dir when '--symfs' is given, so that every
> single file opened by perf is relateive to symfs directory now.
>
> Signed-off-by: He Kuang <hekuang@huawei.com>
> ---
>  tools/perf/builtin-annotate.c  |  5 +++--
>  tools/perf/builtin-diff.c      |  5 +++--
>  tools/perf/builtin-report.c    |  5 +++--
>  tools/perf/builtin-script.c    |  5 +++--
>  tools/perf/builtin-timechart.c |  5 +++--
>  tools/perf/util/dso.c          |  4 +---
>  tools/perf/util/symbol.c       | 23 +++++++++++++++++++++++
>  tools/perf/util/symbol.h       |  2 ++
>  8 files changed, 41 insertions(+), 13 deletions(-)

Acked-by: David Ahern <dsahern@gmail.com>

  reply	other threads:[~2016-05-19 14:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19 11:47 [PATCH v4 0/6] Add support for remote unwind He Kuang
2016-05-19 11:47 ` [PATCH v4 1/6] perf tools: Set buildid dir under symfs when --symfs is provided He Kuang
2016-05-19 14:23   ` David Ahern [this message]
2016-05-19 16:07   ` Jiri Olsa
2016-05-20 17:46   ` [tip:perf/urgent] " tip-bot for He Kuang
2016-05-19 11:47 ` [PATCH v4 2/6] perf tools: Promote proper messages for cross-platform unwind He Kuang
2016-05-19 14:50   ` Arnaldo Carvalho de Melo
2016-05-19 16:19     ` Jiri Olsa
2016-05-20  3:00       ` Hekuang
2016-05-19 16:46   ` Jiri Olsa
2016-05-19 17:15     ` Jiri Olsa
2016-05-20  2:59     ` Hekuang
2016-05-20  9:53       ` Jiri Olsa
2016-05-19 11:47 ` [PATCH v4 3/6] perf tools: Separate local and remote unwind support detection He Kuang
2016-05-19 11:47 ` [PATCH v4 4/6] perf callchain: Add support for cross-platform unwind He Kuang
2016-05-19 11:47 ` [PATCH v4 5/6] perf callchain: Support x86 target platform He Kuang
2016-05-19 11:47 ` [PATCH v4 6/6] perf callchain: Support aarch64 cross-platform He Kuang

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=10081742-ebd5-fa1c-3531-b0afe510d16d@gmail.com \
    --to=dsahern@gmail.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.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).