From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>,
Aswin Chandramouleeswaran <aswin@hp.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] perf lock: misc fixes and enhancements
Date: Thu, 19 Sep 2013 16:00:38 -0300 [thread overview]
Message-ID: <20130919190038.GJ3891@infradead.org> (raw)
In-Reply-To: <1378693159-8747-1-git-send-email-davidlohr@hp.com>
Em Sun, Sep 08, 2013 at 07:19:12PM -0700, Davidlohr Bueso escreveu:
> This patchset is a first in a series of perf-lock enhancements I am working
> on. Overall it is pretty straightforward, dealing with cleanups, and some
> cosmetic changes.
>
> Patches 1-3 deal with some minor fixes and cleanups.
>
> Patch 4 fixes a segfault in the report command when the perf.data
> file is generated by a non perf-lock command.
>
> Patch 5 and 6 are cosmetic changes.
Applied all but patch 5, since Mitake-san had concerns about it, lemme
know if that changed.
Thanks!
- Arnaldo
> Patch 7 allows the tool to report the average wait times.
>
>
> Thanks!
>
> Davidlohr Bueso (7):
> perf lock: remove dead code
> perf lock: return proper code in report_lock_*_event
> perf lock: plug some memleaks
> perf lock: redo __cmd_report
> perf lock: do not cut lock name
> perf lock: limit bad rate precision
> perf lock: account for lock average wait time
>
> tools/perf/Documentation/perf-lock.txt | 2 +-
> tools/perf/builtin-lock.c | 142 ++++++++++++++++-----------------
> 2 files changed, 70 insertions(+), 74 deletions(-)
>
> --
> 1.7.11.7
next prev parent reply other threads:[~2013-09-19 19:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 2:19 [PATCH 0/7] perf lock: misc fixes and enhancements Davidlohr Bueso
2013-09-09 2:19 ` [PATCH 1/7] perf lock: remove dead code Davidlohr Bueso
2013-10-15 5:24 ` [tip:perf/core] perf lock: Remove " tip-bot for Davidlohr Bueso
2013-09-09 2:19 ` [PATCH 2/7] perf lock: return proper code in report_lock_*_event Davidlohr Bueso
2013-10-15 5:24 ` [tip:perf/core] perf lock: Return " tip-bot for Davidlohr Bueso
2013-09-09 2:19 ` [PATCH 3/7] perf lock: plug some memleaks Davidlohr Bueso
2013-09-09 3:01 ` Ramkumar Ramachandra
2013-09-18 17:39 ` Hitoshi Mitake
2013-10-15 5:24 ` [tip:perf/core] perf lock: Plug " tip-bot for Davidlohr Bueso
2013-09-09 2:19 ` [PATCH 4/7] perf lock: redo __cmd_report Davidlohr Bueso
2013-10-15 5:24 ` [tip:perf/core] perf lock: Redo __cmd_report tip-bot for Davidlohr Bueso
2013-09-09 2:19 ` [PATCH 5/7] perf lock: do not cut lock name Davidlohr Bueso
2013-09-18 17:38 ` Hitoshi Mitake
2013-09-09 2:19 ` [PATCH 6/7] perf lock: limit bad rate precision Davidlohr Bueso
2013-10-15 5:24 ` [tip:perf/core] perf lock: Limit " tip-bot for Davidlohr Bueso
2013-09-09 2:19 ` [PATCH 7/7] perf lock: account for lock average wait time Davidlohr Bueso
2013-10-15 5:24 ` [tip:perf/core] perf lock: Account " tip-bot for Davidlohr Bueso
2013-09-19 19:00 ` Arnaldo Carvalho de Melo [this message]
2013-09-20 3:24 ` [PATCH 0/7] perf lock: misc fixes and enhancements Davidlohr Bueso
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=20130919190038.GJ3891@infradead.org \
--to=acme@redhat.com \
--cc=aswin@hp.com \
--cc=davidlohr@hp.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=peterz@infradead.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).