From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: mingo@kernel.org, peterz@infradead.org, namhyung@kernel.org,
jolsa@kernel.org, linux-kernel@vger.kernel.org,
David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH v2 0/6] perf: Add option to specify time window of interest
Date: Tue, 29 Nov 2016 16:15:45 -0300 [thread overview]
Message-ID: <20161129191545.GD23423@kernel.org> (raw)
In-Reply-To: <1480439746-42695-1-git-send-email-dsahern@gmail.com>
Em Tue, Nov 29, 2016 at 10:15:40AM -0700, David Ahern escreveu:
> This series allows users to collect data and analyze a time window of
> interest within the file.
>
> v2
> - renamed perf_time to perf_time_interval
> - changed ../perf.h to perf.h in patch 1
Thanks, applied and pushed out to acme/perf/core.
- Arnaldo
> David Ahern (6):
> perf tool: Add time-based utility functions
> perf tool: Move parse_nsec_time to time-utils.c
> perf script: Add option to specify time window of interest
> perf sched timehist: Add option to specify time window of interest
> perf kmem: Add option to specify time window of interest
> perf report: Add option to specify time window of interest
>
> tools/perf/Documentation/perf-kmem.txt | 7 ++
> tools/perf/Documentation/perf-report.txt | 7 ++
> tools/perf/Documentation/perf-sched.txt | 8 +++
> tools/perf/Documentation/perf-script.txt | 7 ++
> tools/perf/builtin-kmem.c | 24 +++++++
> tools/perf/builtin-report.c | 14 +++-
> tools/perf/builtin-sched.c | 51 +++++++++++--
> tools/perf/builtin-script.c | 15 +++-
> tools/perf/util/Build | 1 +
> tools/perf/util/time-utils.c | 118 +++++++++++++++++++++++++++++++
> tools/perf/util/time-utils.h | 14 ++++
> tools/perf/util/util.c | 33 ---------
> tools/perf/util/util.h | 2 -
> 13 files changed, 258 insertions(+), 43 deletions(-)
> create mode 100644 tools/perf/util/time-utils.c
> create mode 100644 tools/perf/util/time-utils.h
>
> --
> 2.7.4 (Apple Git-66)
next prev parent reply other threads:[~2016-11-29 19:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 17:15 [PATCH v2 0/6] perf: Add option to specify time window of interest David Ahern
2016-11-29 17:15 ` [PATCH v2 1/6] perf tool: Add time-based utility functions David Ahern
2016-12-02 10:41 ` [tip:perf/core] perf tools: " tip-bot for David Ahern
2016-11-29 17:15 ` [PATCH v2 2/6] perf tool: Move parse_nsec_time to time-utils.c David Ahern
2016-12-02 10:41 ` [tip:perf/core] perf tools: " tip-bot for David Ahern
2016-11-29 17:15 ` [PATCH v2 3/6] perf script: Add option to specify time window of interest David Ahern
2016-12-02 10:42 ` [tip:perf/core] " tip-bot for David Ahern
2016-11-29 17:15 ` [PATCH v2 4/6] perf sched timehist: " David Ahern
2016-11-29 18:56 ` Arnaldo Carvalho de Melo
2016-11-29 18:58 ` David Ahern
2016-11-29 19:21 ` Arnaldo Carvalho de Melo
2016-12-02 10:42 ` [tip:perf/core] " tip-bot for David Ahern
2016-11-29 17:15 ` [PATCH v2 5/6] perf kmem: " David Ahern
2016-12-02 10:43 ` [tip:perf/core] " tip-bot for David Ahern
2016-11-29 17:15 ` [PATCH v2 6/6] perf report: " David Ahern
2016-12-02 10:43 ` [tip:perf/core] " tip-bot for David Ahern
2016-11-29 19:15 ` Arnaldo Carvalho de Melo [this message]
2016-11-30 5:26 ` [PATCH v2 0/6] perf: " Namhyung Kim
2016-11-30 14:23 ` Arnaldo Carvalho de Melo
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=20161129191545.GD23423@kernel.org \
--to=acme@kernel.org \
--cc=dsa@cumulusnetworks.com \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--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).