From: Namhyung Kim <namhyung@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>,
acme@ghostprotocols.net, LKML <linux-kernel@vger.kernel.org>,
jmario@redhat.com, fowles@inreach.com
Subject: Re: [PATCH 3/4] perf, callchain: Add generic report parse callchain callback function
Date: Mon, 07 Apr 2014 14:15:21 +0900 [thread overview]
Message-ID: <87r459yb2u.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20140406121129.GB1164@krava.brq.redhat.com> (Jiri Olsa's message of "Sun, 6 Apr 2014 14:11:29 +0200")
Hi Jiri and Don,
On Sun, 6 Apr 2014 14:11:29 +0200, Jiri Olsa wrote:
> On Fri, Apr 04, 2014 at 03:31:19PM -0400, Don Zickus wrote:
>> On Thu, Apr 03, 2014 at 02:57:32PM +0900, Namhyung Kim wrote:
>> > On Mon, 24 Mar 2014 15:32:56 -0400, Don Zickus wrote:
>> > > This takes the parse_callchain_opt function and copies it into the
>> > > callchain.c file. Now the c2c tool can use it too without duplicating.
>> > >
>> > > Signed-off-by: Don Zickus <dzickus@redhat.com>
>> > > ---
>> > > tools/perf/util/callchain.c | 83 +++++++++++++++++++++++++++++++++++++++++++++
>> > > tools/perf/util/callchain.h | 1 +
>> > > 2 files changed, 84 insertions(+)
>> > >
>> > > diff --git a/tools/perf/util/callchain.c b/tools/perf/util/callchain.c
>> > > index 8d9db45..2320678 100644
>> > > --- a/tools/perf/util/callchain.c
>> > > +++ b/tools/perf/util/callchain.c
>> > > @@ -25,6 +25,89 @@
>> > >
>> > > __thread struct callchain_cursor callchain_cursor;
>> > >
>> > > +int
>> > > +report_parse_callchain_opt(const char *arg)
>> >
>> > As it eliminated any dependency to the report code, the name can omit
>> > 'report' as well.
>>
>> Hmm, shrinking this down to 'parse_callchain_opt' seems to conflict with
>> builtin-top.c's defintion which is a wrapper around
>> record_parse_callchain_opt.
>>
>> I can modify builtin-top.c's defintion to top_parse_callchain_opt, but do
>> we want to make the function parse_callchain_opt name more obvious that it is
>> for 'report' style parsing (which means it looks for the embedded
>> callchain flag)? Vs. the record_parse_callchain_opt function, which is for
>> setting up the callchain flag?
>
> that sounds good to me.. (record|report)_parse_callchain_opt
Agreed. Maybe parse_callchain_(record|report)_opt?
Thanks,
Namhyung
next prev parent reply other threads:[~2014-04-07 5:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 19:32 [PATCH 0/4] perf: Make some functions generic Don Zickus
2014-03-24 19:32 ` [PATCH 1/4] perf: Allow ability to map cpus to nodes easily Don Zickus
2014-03-29 17:10 ` Jiri Olsa
2014-04-01 2:39 ` Don Zickus
2014-04-06 12:19 ` Jiri Olsa
2014-04-03 5:48 ` Namhyung Kim
2014-04-06 12:15 ` Jiri Olsa
2014-04-07 5:28 ` Namhyung Kim
2014-04-07 18:20 ` Don Zickus
2014-03-24 19:32 ` [PATCH 2/4] perf, kmem: Utilize the new generic cpunode_map Don Zickus
2014-03-29 17:10 ` Jiri Olsa
2014-04-01 2:42 ` Don Zickus
2014-04-06 12:21 ` Jiri Olsa
2014-04-07 18:18 ` Don Zickus
2014-03-24 19:32 ` [PATCH 3/4] perf, callchain: Add generic report parse callchain callback function Don Zickus
2014-03-29 17:11 ` Jiri Olsa
2014-04-03 5:57 ` Namhyung Kim
2014-04-04 19:31 ` Don Zickus
2014-04-06 12:11 ` Jiri Olsa
2014-04-07 5:15 ` Namhyung Kim [this message]
2014-04-07 7:01 ` Jiri Olsa
2014-03-24 19:32 ` [PATCH 4/4] perf, report: Use new generic report parse callchain callback Don Zickus
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=87r459yb2u.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=acme@ghostprotocols.net \
--cc=dzickus@redhat.com \
--cc=fowles@inreach.com \
--cc=jmario@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome