From: Waiman Long <Waiman.Long@hp.com>
To: Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Adrian Hunter <adrian.hunter@intel.com>,
David Ahern <dsahern@gmail.com>,
Stephane Eranian <eranian@google.com>,
linux-kernel@vger.kernel.org,
Aswin Chandramouleeswaran <aswin@hp.com>,
Scott J Norton <scott.norton@hp.com>,
Waiman Long <Waiman.Long@hp.com>
Subject: [PATCH v2 0/4] perf: add option to limit callchain stack scan to increase speed
Date: Fri, 18 Oct 2013 10:38:45 -0400 [thread overview]
Message-ID: <1382107129-2010-1-git-send-email-Waiman.Long@hp.com> (raw)
v1->v2:
- Include a compilation fix patch and a code streamlining patch
into the patch set.
- Use the __stringify() macro in stringify.h instead of adding a
duplicate macro.
- Add the --max-stack option to perf-top as well.
This perf patch set contains the following changes:
Patch 1 - Fix a perf tool compilation error that happens on SLES 11
sp3 system.
Patch 2 - Streamline the append_chain() function to make it run a bit
faster.
Patch 3 - Add a --max-stack option to perf-report to speed up its
processing at the expense of less backtrace information
available.
Patch 4 - Add a similar --max-stack option to perf-top.
Waiman Long (4):
perf: Fix potential compilation error with some compilers
perf: streamline append_chain() function
perf-report: add --max-stack option to limit callchain stack scan
perf-top: add --max-stack option to limit callchain stack scan
tools/perf/Documentation/perf-report.txt | 8 +++++++
tools/perf/Documentation/perf-top.txt | 8 +++++++
tools/perf/builtin-report.c | 22 +++++++++++++++----
tools/perf/builtin-top.c | 9 ++++++-
tools/perf/util/callchain.c | 9 +++----
tools/perf/util/machine.c | 14 ++++++++----
tools/perf/util/machine.h | 3 +-
.../perf/util/scripting-engines/trace-event-perl.c | 6 ++++-
tools/perf/util/session.c | 3 +-
tools/perf/util/top.h | 1 +
10 files changed, 63 insertions(+), 20 deletions(-)
next reply other threads:[~2013-10-18 14:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 14:38 Waiman Long [this message]
2013-10-18 14:38 ` [PATCH v2 1/4] perf: Fix potential compilation error with some compilers Waiman Long
2013-10-18 14:38 ` [PATCH v2 2/4] perf: streamline append_chain() function Waiman Long
2013-10-20 0:29 ` Andi Kleen
2013-10-21 14:50 ` Waiman Long
2013-10-18 14:38 ` [PATCH v2 3/4] perf-report: add --max-stack option to limit callchain stack scan Waiman Long
2013-10-18 17:17 ` Arnaldo Carvalho de Melo
2013-10-21 14:51 ` Waiman Long
2013-10-18 17:30 ` David Ahern
2013-10-23 7:55 ` [tip:perf/core] perf report: Add " tip-bot for Waiman Long
2013-10-18 14:38 ` [PATCH v2 4/4] perf-top: add " Waiman Long
2013-10-18 17:31 ` David Ahern
2013-10-20 22:35 ` Davidlohr Bueso
2013-10-23 7:55 ` [tip:perf/core] perf top: Add " tip-bot for Waiman Long
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=1382107129-2010-1-git-send-email-Waiman.Long@hp.com \
--to=waiman.long@hp.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=adrian.hunter@intel.com \
--cc=aswin@hp.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=scott.norton@hp.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
Powered by JetHome