From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Jiri Olsa <jolsa@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [RFC 00/13] perf test: Add perf_event_attr tests
Date: Fri, 24 Aug 2012 10:07:06 -0300 [thread overview]
Message-ID: <20120824130706.GA27708@infradead.org> (raw)
In-Reply-To: <1345798844-27423-1-git-send-email-jolsa@redhat.com>
Em Fri, Aug 24, 2012 at 11:00:31AM +0200, Jiri Olsa escreveu:
> tools/perf/util/test-attr.c | 142 ++++++++++++++++++++++++++
> tools/perf/util/test-attr.py | 272 ++++++++++++++++++++++++++++++++++++++++++++++++++
> tools/perf/util/test-attr/base-record | 39 ++++++++
I suggest we move all this to:
tools/perf/tests/attr/
> tools/perf/util/test-attr/base-stat | 39 ++++++++
> tools/perf/util/test-attr/test-record-basic | 5 +
> tools/perf/util/test-attr/test-record-count | 8 ++
> tools/perf/util/test-attr/test-record-freq | 6 ++
> tools/perf/util/test-attr/test-record-graph-default | 6 ++
> tools/perf/util/test-attr/test-record-graph-dwarf | 6 ++
> tools/perf/util/test-attr/test-record-graph-fp | 6 ++
> tools/perf/util/test-attr/test-record-group | 17 ++++
> tools/perf/util/test-attr/test-record-no-inherit | 7 ++
> tools/perf/util/test-attr/test-record-no-samples | 6 ++
> tools/perf/util/test-attr/test-record-period | 7 ++
> tools/perf/util/test-attr/test-stat-basic | 6 ++
> tools/perf/util/test-attr/test-stat-group | 15 +++
> tools/perf/util/test-attr/test-stat-no-inherit | 7 ++
> 21 files changed, 612 insertions(+)
next prev parent reply other threads:[~2012-08-24 13:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 9:00 [RFC 00/13] perf test: Add perf_event_attr tests Jiri Olsa
2012-08-24 9:00 ` [PATCH 01/13] perf test: Add framework for atomated " Jiri Olsa
2012-08-24 9:00 ` [PATCH 02/13] perf test: Add perf_event_attr record basic test Jiri Olsa
2012-08-24 9:00 ` [PATCH 03/13] perf test: Add perf_event_attr record group test Jiri Olsa
2012-08-24 9:00 ` [PATCH 04/13] perf test: Add perf_event_attr record freq test Jiri Olsa
2012-08-24 9:00 ` [PATCH 05/13] perf test: Add perf_event_attr record count test Jiri Olsa
2012-08-24 9:00 ` [PATCH 06/13] perf test: Add perf_event_attr record graph test Jiri Olsa
2012-08-24 9:00 ` [PATCH 07/13] perf test: Add perf_event_attr record period test Jiri Olsa
2012-08-24 9:00 ` [PATCH 08/13] perf test: Add perf_event_attr record no samples test Jiri Olsa
2012-08-24 9:00 ` [PATCH 09/13] perf test: Add perf_event_attr record no-inherit test Jiri Olsa
2012-08-24 9:00 ` [PATCH 10/13] perf test: Add perf_event_attr stat basic test Jiri Olsa
2012-08-24 9:00 ` [PATCH 11/13] perf test: Add perf_event_attr stat no-inherit test Jiri Olsa
2012-08-24 9:00 ` [PATCH 12/13] perf test: Add perf_event_attr stat group test Jiri Olsa
2012-08-24 9:00 ` [PATCH 13/13] perf test: Add attr tests under builtin test command Jiri Olsa
2012-08-24 13:07 ` Arnaldo Carvalho de Melo [this message]
2012-08-24 18:12 ` [RFC 00/13] perf test: Add perf_event_attr tests Ingo Molnar
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=20120824130706.GA27708@infradead.org \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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