From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Jiri Olsa <jolsa@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH 5/7] perf ui/stdio: Reset output width for hierarchy
Date: Mon, 12 Sep 2016 11:27:28 -0300 [thread overview]
Message-ID: <20160912142728.GD4897@kernel.org> (raw)
In-Reply-To: <20160912061958.16656-6-namhyung@kernel.org>
Em Mon, Sep 12, 2016 at 03:19:56PM +0900, Namhyung Kim escreveu:
> When --hierarchy option is used, each entry has its own hpp_list to show
> the result. But it missed to update width of each column.
Missing "Fixes:" tag? This is important for the stable series, that IIRC
uses those tags to semi-automatically figure out what should be picked.
- Arnaldo
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
> tools/perf/ui/stdio/hist.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/tools/perf/ui/stdio/hist.c b/tools/perf/ui/stdio/hist.c
> index 9b65f4a6b35a..83ca728b6f61 100644
> --- a/tools/perf/ui/stdio/hist.c
> +++ b/tools/perf/ui/stdio/hist.c
> @@ -733,6 +733,7 @@ size_t hists__fprintf(struct hists *hists, bool show_header, int max_rows,
> bool use_callchain)
> {
> struct perf_hpp_fmt *fmt;
> + struct perf_hpp_list_node *node;
> struct rb_node *nd;
> size_t ret = 0;
> const char *sep = symbol_conf.field_sep;
> @@ -745,6 +746,11 @@ size_t hists__fprintf(struct hists *hists, bool show_header, int max_rows,
>
> hists__for_each_format(hists, fmt)
> perf_hpp__reset_width(fmt, hists);
> + /* hierarchy entries have their own hpp list */
> + list_for_each_entry(node, &hists->hpp_formats, list) {
> + perf_hpp_list__for_each_format(&node->hpp, fmt)
> + perf_hpp__reset_width(fmt, hists);
> + }
>
> if (symbol_conf.col_width_list_str)
> perf_hpp__set_user_width(symbol_conf.col_width_list_str);
> --
> 2.9.3
next prev parent reply other threads:[~2016-09-12 14:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 6:19 [PATCHSET 0/7] perf tools: Support hierarchy report with event group (v1) Namhyung Kim
2016-09-12 6:19 ` [PATCH 1/7] perf hists browser: Fix event group display Namhyung Kim
2016-09-12 14:23 ` Arnaldo Carvalho de Melo
2016-09-20 21:37 ` [tip:perf/core] " tip-bot for Namhyung Kim
2016-09-12 6:19 ` [PATCH 2/7] perf hist: Introduce hists__match_hierarchy() Namhyung Kim
2016-09-12 14:25 ` Arnaldo Carvalho de Melo
2016-09-12 23:59 ` Namhyung Kim
2016-09-12 6:19 ` [PATCH 3/7] perf hist: Introduce hists__link_hierarchy() Namhyung Kim
2016-09-12 6:19 ` [PATCH 4/7] perf hist: Initialize hierachy tree explicitly Namhyung Kim
2016-09-12 14:22 ` Arnaldo Carvalho de Melo
2016-09-13 0:09 ` Namhyung Kim
2016-09-12 6:19 ` [PATCH 5/7] perf ui/stdio: Reset output width for hierarchy Namhyung Kim
2016-09-12 14:27 ` Arnaldo Carvalho de Melo [this message]
2016-09-13 1:00 ` Namhyung Kim
2016-09-12 6:19 ` [PATCH 6/7] perf ui/tui: " Namhyung Kim
2016-09-12 14:27 ` Arnaldo Carvalho de Melo
2016-09-13 1:01 ` Namhyung Kim
2016-09-12 6:19 ` [PATCH 7/7] perf report: Enable group view with hierarchy Namhyung Kim
2016-09-12 14:28 ` Arnaldo Carvalho de Melo
2016-09-13 1:06 ` Namhyung Kim
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=20160912142728.GD4897@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@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;
as well as URLs for NNTP newsgroup(s).