From: Hekuang <hekuang@huawei.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>, Jiri Olsa <jolsa@redhat.com>
Cc: <peterz@infradead.org>, <mingo@redhat.com>,
<alexander.shishkin@linux.intel.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 1/8] perf tools: Omit DWARF judgement when recording dwarf callchain
Date: Tue, 10 May 2016 09:44:48 +0800 [thread overview]
Message-ID: <57313D10.5040808@huawei.com> (raw)
In-Reply-To: <20160509161649.GA3903@kernel.org>
ok
在 2016/5/10 0:16, Arnaldo Carvalho de Melo 写道:
> Em Sat, May 07, 2016 at 08:03:46PM +0200, Jiri Olsa escreveu:
>> On Fri, May 06, 2016 at 08:59:07AM +0000, He Kuang wrote:
>>> There's no need for dwarf support when perf recording with callchain.
>>>
>>> Signed-off-by: He Kuang <hekuang@huawei.com>
>> Acked-by: Jiri Olsa <jolsa@kernel.org>
> Ok, due to your Ack I went on to read the code and indeed, with this
> changeset description:
>
> "There is no need to check for DWARF unwinding support when using the
> 'dwarf' callchain record method, as this will only ask the kernel to
> collect stack dumps for later DWARF CFI processing, which can be done
> in another machine, where the support for DWARF unwinding need to be
> present."
>
> Thanks,
>
> - Arnaldo
>
>> thanks,
>> jirka
>>
>>> ---
>>> tools/perf/util/util.c | 2 --
>>> 1 file changed, 2 deletions(-)
>>>
>>> diff --git a/tools/perf/util/util.c b/tools/perf/util/util.c
>>> index b7766c5..e5ebfd4 100644
>>> --- a/tools/perf/util/util.c
>>> +++ b/tools/perf/util/util.c
>>> @@ -471,7 +471,6 @@ int parse_callchain_record(const char *arg, struct callchain_param *param)
>>> "needed for --call-graph fp\n");
>>> break;
>>>
>>> -#ifdef HAVE_DWARF_UNWIND_SUPPORT
>>> /* Dwarf style */
>>> } else if (!strncmp(name, "dwarf", sizeof("dwarf"))) {
>>> const unsigned long default_stack_dump_size = 8192;
>>> @@ -487,7 +486,6 @@ int parse_callchain_record(const char *arg, struct callchain_param *param)
>>> ret = get_stack_size(tok, &size);
>>> param->dump_size = size;
>>> }
>>> -#endif /* HAVE_DWARF_UNWIND_SUPPORT */
>>> } else if (!strncmp(name, "lbr", sizeof("lbr"))) {
>>> if (!strtok_r(NULL, ",", &saveptr)) {
>>> param->record_mode = CALLCHAIN_LBR;
>>> --
>>> 1.8.5.2
>>>
next prev parent reply other threads:[~2016-05-10 1:47 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 [this message]
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
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=57313D10.5040808@huawei.com \
--to=hekuang@huawei.com \
--cc=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=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
Powered by JetHome