public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: [PATCH 0/5] perf tools: Add support for multiline headers and spans
Date: Sun,  7 Aug 2016 17:28:25 +0200	[thread overview]
Message-ID: <1470583710-1649-1-git-send-email-jolsa@kernel.org> (raw)

hi,
the c2c output readability heavily depends on headers
being displayed on multiple lines and allowing span
of some headers over multiple columns, like:

#                                Total     %All             Total  ----- Core Load Hit -----  -- LLC Load Hit --  ----- LLC Load Hitm -----
# Index             Cacheline  records  Ld Miss    %hitm    Loads       FB       L1       L2       Llc       Rmt    Total      Lcl      Rmt
# .....  ....................  .......  .......  .......  .......  .......  .......  .......  ........  ........  .......  .......  .......
#
      0        0x7fbe65acee00      203    2.37%    3.34%      162       26       72        0        20         2       39       11       28


I haven't found use for this under current perf code,
so there's no actual current user in perf code of
those features.

Also available in:
  git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
  perf/fixes

thanks,
jirka

---
Jiri Olsa (5):
      perf tools: Introduce nr_header_lines into struct perf_hpp_list
      perf tools: Add line argument into perf_hpp_fmt's header callback
      perf tools tui: Display multiple header lines
      perf tools stdio: Display multiple header lines
      perf tools: Add support for header span

 tools/perf/builtin-diff.c      |  4 +++-
 tools/perf/ui/browsers/hists.c | 48 +++++++++++++++++++++++++++++++++++-------------
 tools/perf/ui/gtk/hists.c      |  2 +-
 tools/perf/ui/hist.c           |  4 +++-
 tools/perf/ui/stdio/hist.c     | 45 ++++++++++++++++++++++++++++++++-------------
 tools/perf/util/hist.h         |  3 ++-
 tools/perf/util/sort.c         |  7 +++++--
 7 files changed, 81 insertions(+), 32 deletions(-)

             reply	other threads:[~2016-08-07 15:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-07 15:28 Jiri Olsa [this message]
2016-08-07 15:28 ` [PATCH 1/5] perf tools: Introduce nr_header_lines into struct perf_hpp_list Jiri Olsa
2016-08-24  9:19   ` [tip:perf/core] perf hists: " tip-bot for Jiri Olsa
2016-08-07 15:28 ` [PATCH 2/5] perf tools: Add line argument into perf_hpp_fmt's header callback Jiri Olsa
2016-08-24  9:19   ` [tip:perf/core] perf hists: " tip-bot for Jiri Olsa
2016-08-07 15:28 ` [PATCH 3/5] perf tools tui: Display multiple header lines Jiri Olsa
2016-08-24  9:20   ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-08-07 15:28 ` [PATCH 4/5] perf tools stdio: " Jiri Olsa
2016-08-24  9:20   ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-08-07 15:28 ` [PATCH 5/5] perf tools: Add support for header span Jiri Olsa
2016-08-24  9:21   ` [tip:perf/core] perf hists: " tip-bot for Jiri Olsa

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=1470583710-1649-1-git-send-email-jolsa@kernel.org \
    --to=jolsa@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=dsahern@gmail.com \
    --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