From: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
To: dsahern@gmail.com, jolsa@redhat.com, acme@ghostprotocols.net,
mingo@redhat.com, a.p.zijlstra@chello.nl, paulus@samba.org
Cc: linux-kernel@vger.kernel.org,
Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
Subject: [PATCH 0/5] perf tools: some update for perf tool.
Date: Wed, 4 Dec 2013 17:56:38 -0500 [thread overview]
Message-ID: <cover.1386197481.git.yangds.fnst@cn.fujitsu.com> (raw)
Hi all,
When I read the code and document of perf tool as a newbie,
I feel confused in some places. Then I made some patches here to make
them more clear.
Please help to review them.
Note: The last 3 commits are all about perf-kvm.txt. I splite them
to make the logic more clear. If you think it is not necessary, I am
ok to squash them into one commit.
Thanx
Yang
Dongsheng Yang (5):
perf tools: Remove condition in machine__get_kernel_start_addr.
perf tools: Move the checking of which map function to call into
function.
perf tools: Update the Document for perf kvm record for new behavior.
perf tools: Add more detail about buildid-list in Document of
perf-kvm.
perf tool: Fix a type of '=' in Document of perf-kvm.
tools/perf/Documentation/perf-kvm.txt | 27 ++++++++++++++++++---------
tools/perf/util/evlist.c | 8 +-------
tools/perf/util/machine.c | 14 +++++---------
tools/perf/util/target.h | 13 +++++++++++++
4 files changed, 37 insertions(+), 25 deletions(-)
--
1.8.2.1
next reply other threads:[~2013-12-04 9:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 22:56 Dongsheng Yang [this message]
2013-12-04 22:56 ` [PATCH 1/5] perf tools: Remove condition in machine__get_kernel_start_addr Dongsheng Yang
2013-12-10 9:16 ` [tip:perf/core] " tip-bot for Dongsheng Yang
2013-12-04 22:56 ` [PATCH 2/5] perf tools: Move the checking of which map function to call into function Dongsheng Yang
2013-12-10 9:16 ` [tip:perf/core] perf target: " tip-bot for Dongsheng Yang
2013-12-04 22:56 ` [PATCH 3/5] perf tools: Update the Document for perf kvm record for new behavior Dongsheng Yang
2013-12-04 14:27 ` Arnaldo Carvalho de Melo
2013-12-05 21:55 ` Dongsheng Yang
2013-12-10 9:17 ` [tip:perf/core] perf kvm: Update the 'record' man page entry for new --guest/--host behavior tip-bot for Dongsheng Yang
2013-12-04 22:56 ` [PATCH 4/5] perf tools: Add more detail about buildid-list in Document of perf-kvm Dongsheng Yang
2013-12-10 9:16 ` [tip:perf/core] perf kvm: Add more detail about buildid-list in man page tip-bot for Dongsheng Yang
2013-12-04 22:56 ` [PATCH 5/5] perf tool: Fix a type of '=' in Document of perf-kvm Dongsheng Yang
2013-12-10 9:16 ` [tip:perf/core] perf kvm: Fix spurious '=' use in man page tip-bot for Dongsheng Yang
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=cover.1386197481.git.yangds.fnst@cn.fujitsu.com \
--to=yangds.fnst@cn.fujitsu.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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