From: Jin Yao <yao.jin@linux.intel.com>
To: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com
Cc: Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com,
Jin Yao <yao.jin@linux.intel.com>
Subject: [PATCH v5 0/4] perf: Refactor the block info implementation
Date: Tue, 28 Jan 2020 20:55:52 +0800 [thread overview]
Message-ID: <20200128125556.25498-1-yao.jin@linux.intel.com> (raw)
This patch series refactors the block info functionalities to let them
be used by other builtins and allow setting the output fmts flexibly.
It also supports the 'Sampled Cycles%' and 'Avg Cycles%' printed in
colors.
v5:
---
Only change the patch "perf util: Flexible to set block info output formats".
Other patches are not changed.
Jin Yao (4):
perf util: Move block_pair_cmp to block-info
perf util: Validate map/dso/sym before comparing blocks
perf util: Flexible to set block info output formats
perf util: Support color ops to print block percents in color
tools/perf/builtin-diff.c | 17 -------
tools/perf/builtin-report.c | 21 ++++++--
tools/perf/util/block-info.c | 99 ++++++++++++++++++++++++++----------
tools/perf/util/block-info.h | 9 +++-
4 files changed, 99 insertions(+), 47 deletions(-)
--
2.17.1
next reply other threads:[~2020-01-28 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 12:55 Jin Yao [this message]
2020-01-28 12:55 ` [PATCH v5 1/4] perf util: Move block_pair_cmp to block-info Jin Yao
2020-01-31 8:32 ` Arnaldo Carvalho de Melo
2020-01-31 11:52 ` Jin, Yao
2020-01-28 12:55 ` [PATCH v5 2/4] perf util: Validate map/dso/sym before comparing blocks Jin Yao
2020-01-28 12:55 ` [PATCH v5 3/4] perf util: Flexible to set block info output formats Jin Yao
2020-01-28 12:55 ` [PATCH v5 4/4] perf util: Support color ops to print block percents in color Jin Yao
2020-01-30 16:02 ` [PATCH v5 0/4] perf: Refactor the block info implementation 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=20200128125556.25498-1-yao.jin@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.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;
as well as URLs for NNTP newsgroup(s).