From: Andi Kleen <andi@firstfloor.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
jolsa@kernel.org, acme@kernel.org, mingo@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: perf, tools: Refactor and support interval and CSV metrics v6
Date: Thu, 5 Nov 2015 03:43:50 +0100 [thread overview]
Message-ID: <20151105024350.GB3533@two.firstfloor.org> (raw)
In-Reply-To: <20151103074616.GE23878@krava.brq.redhat.com>
On Tue, Nov 03, 2015 at 08:46:16AM +0100, Jiri Olsa wrote:
> On Mon, Nov 02, 2015 at 05:50:19PM -0800, Andi Kleen wrote:
> > [v4: Addressed all review feedback.]
> > [v3: Addressed all review feedback. Update manpage for CSV. Various changes
> > (see individual patches). Remove some more redundant code
> > in printout callers.]
> > [v2: Addressed (near) all review feedback. No manpage updates so far.
> > Add support for --per-core metrics. Various cleanups.]
> > [v3: Everything compiles again. Some more cleanups.]
> > [v4: Split up abstract metrics patch into two. Fix bug with earlier
> > patch already enabling metrics for CSV/interval. Minor cleanups.
> > Man page is included]
> > [v5: Fix mainly bisect problems. No regressions introduced by one
> > patch and fixed again later. Some minor fixes in addition]
> > [v6: Fix running/noise printing patch.]
>
> I like the list.. starting with v4 goes down to v2 and raise again to v6 ;-)
Oops. I switched order at some point. Will fix.
-Andi
>
> I'll try to check it this week
>
> thanks,
> jirka
>
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2015-11-05 2:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 1:50 perf, tools: Refactor and support interval and CSV metrics v6 Andi Kleen
2015-11-03 1:50 ` [PATCH 1/9] perf, tools, stat: Move sw clock metrics printout to stat-shadow Andi Kleen
2015-11-04 8:15 ` Jiri Olsa
2015-11-08 7:28 ` [tip:perf/urgent] perf " tip-bot for Andi Kleen
2015-11-03 1:50 ` [PATCH 2/9] tools, perf, stat: Use common printout faction to avoid duplicated code Andi Kleen
2015-11-04 8:15 ` Jiri Olsa
2015-11-08 7:28 ` [tip:perf/urgent] perf stat: Use common printout function " tip-bot for Andi Kleen
2015-11-03 1:50 ` [PATCH 3/9] perf, tools, stat: Abstract stat metrics printing Andi Kleen
2015-11-04 8:34 ` Jiri Olsa
2015-11-04 8:42 ` Jiri Olsa
2015-11-05 2:43 ` Andi Kleen
2015-11-05 6:52 ` Jiri Olsa
2015-11-05 15:20 ` Andi Kleen
2015-11-03 1:50 ` [PATCH 4/9] perf, tools, stat: Add support for metrics in interval mode Andi Kleen
2015-11-03 1:50 ` [PATCH 5/9] perf, tools, stat: Move noise/running printing into printout Andi Kleen
2015-11-04 8:48 ` Jiri Olsa
2015-11-03 1:50 ` [PATCH 6/9] perf, tools, stat: Implement CSV metrics output Andi Kleen
2015-11-03 1:50 ` [PATCH 7/9] perf, tools, stat: Move non counting counter printing to printout Andi Kleen
2015-11-03 1:50 ` [PATCH 8/9] perf, tools: Support metrics in --per-core/socket mode Andi Kleen
2015-11-03 1:50 ` [PATCH 9/9] perf, tools, stat: Document CSV format in manpage Andi Kleen
2015-11-03 7:46 ` perf, tools: Refactor and support interval and CSV metrics v6 Jiri Olsa
2015-11-05 2:43 ` Andi Kleen [this message]
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=20151105024350.GB3533@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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).