From: Namhyung Kim <namhyung@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Andi Kleen <andi@firstfloor.org>,
Stephane Eranian <eranian@google.com>,
Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH 2/8] perf tools: Introduce perf_hpp__setup_hists_formats()
Date: Fri, 4 Mar 2016 08:52:13 +0900 [thread overview]
Message-ID: <20160303235213.GB16631@sejong> (raw)
In-Reply-To: <20160303134022.GA5487@krava.redhat.com>
Hi Jiri,
On Thu, Mar 03, 2016 at 02:40:22PM +0100, Jiri Olsa wrote:
> On Thu, Mar 03, 2016 at 01:12:02AM +0900, Namhyung Kim wrote:
>
> SNIP
>
> > +struct perf_hpp_fmt *perf_hpp_fmt__copy(struct perf_hpp_fmt *fmt);
> > +
> > int hist_entry__filter(struct hist_entry *he, int type, const void *arg);
> >
> > static inline bool perf_hpp__should_skip(struct perf_hpp_fmt *format,
> > diff --git a/tools/perf/util/sort.c b/tools/perf/util/sort.c
> > index 590ebf70e6da..29c75f0374c4 100644
> > --- a/tools/perf/util/sort.c
> > +++ b/tools/perf/util/sort.c
> > @@ -1908,6 +1908,31 @@ __alloc_dynamic_entry(struct perf_evsel *evsel, struct format_field *field,
> > return hde;
> > }
> >
> > +struct perf_hpp_fmt *perf_hpp_fmt__copy(struct perf_hpp_fmt *fmt)
>
> perf_hpp_fmt__dup might be better
OK
>
> > +{
> > + struct perf_hpp_fmt *new_fmt = NULL;
> > +
> > + if (perf_hpp__is_sort_entry(fmt)) {
> > + struct hpp_sort_entry *hse, *new_hse;
> > +
> > + hse = container_of(fmt, struct hpp_sort_entry, hpp);
> > + new_hse = memdup(hse, sizeof(*hse));
> > + if (new_hse)
> > + new_fmt = &new_hse->hpp;
> > + } else if (perf_hpp__is_dynamic_entry(fmt)) {
> > + struct hpp_dynamic_entry *hde, *new_hde;
> > +
> > + hde = container_of(fmt, struct hpp_dynamic_entry, hpp);
> > + new_hde = memdup(hde, sizeof(*hde));
> > + if (new_hde)
> > + new_fmt = &new_hde->hpp;
> > + } else {
> > + new_fmt = memdup(fmt, sizeof(*fmt));
> > + }
>
> how about also initialize new_fmt's list and sort_list in here
>
> could save some time in future if perf_hpp_fmt__copy is
> used in another place, which won't directly initialize them
> like you do in add_hierarchy_fmt
Fair enough, will change.
Thanks,
Namhyung
next prev parent reply other threads:[~2016-03-03 23:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 16:12 [PATCHSET 0/8] perf tools: Support multiple keys in a single hierarchy level (v1) Namhyung Kim
2016-03-02 16:12 ` [PATCH 1/8] perf tools: Add level field to struct perf_hpp_fmt Namhyung Kim
2016-03-02 16:12 ` [PATCH 2/8] perf tools: Introduce perf_hpp__setup_hists_formats() Namhyung Kim
2016-03-03 13:40 ` Jiri Olsa
2016-03-03 23:52 ` Namhyung Kim [this message]
2016-03-03 13:40 ` Jiri Olsa
2016-03-03 23:53 ` Namhyung Kim
2016-03-02 16:12 ` [PATCH 3/8] perf tools: Use own hpp_list for hierarchy mode Namhyung Kim
2016-03-02 16:12 ` [PATCH 4/8] perf tools: Support multiple sort keys in a hierarchy Namhyung Kim
2016-03-02 16:12 ` [PATCH 5/8] perf tools: Fix indent for multiple hierarchy sort key Namhyung Kim
2016-03-02 16:12 ` [PATCH 6/8] perf report: Use hierarchy hpp list on stdio Namhyung Kim
2016-03-02 16:12 ` [PATCH 7/8] perf hists browser: Use hierarchy hpp list Namhyung Kim
2016-03-02 16:12 ` [PATCH 8/8] perf report: Use hierarchy hpp list on gtk Namhyung Kim
2016-03-02 16:25 ` [PATCHSET 0/8] perf tools: Support multiple keys in a single hierarchy level (v1) Arnaldo Carvalho de Melo
2016-03-02 23:16 ` Namhyung Kim
2016-03-03 13:08 ` [RFC] " Arnaldo Carvalho de Melo
2016-03-03 23:50 ` Namhyung Kim
2016-03-04 13:32 ` 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=20160303235213.GB16631@sejong \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--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