All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
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: [PATCH 00/25] perf test: Add perf_event_attr tests
Date: Fri, 2 Nov 2012 00:20:56 +0100	[thread overview]
Message-ID: <20121101232055.GA1690@krava.redhat.com> (raw)
In-Reply-To: <20121101203800.GA3911@ghostprotocols.net>

On Thu, Nov 01, 2012 at 05:38:01PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Oct 30, 2012 at 11:01:41PM +0100, Jiri Olsa escreveu:
> > hi,
> > this code tests the link between perf stat/record command line
> > options and final perf_event_attr struct values. Also it tests
> > the group fd linkage.
> > 
> > Plus moving test related objects under 'test' directory.
> 
> Ok, so I applied this to my local perf/core branch with a few changes,
> namely to move 24/25 to after 5/25 so that I could do, for each
> subsequent tests:
> 
> $ make -j8 -C tools/perf/ O=/home/acme/git/build/perf install
> $ perf test -v perf_event_attr
> 
> And see if each one passed.
> 
> So at the end I changed
> /home/acme/libexec/perf-core/tests/attr/base-record flipping
> "watermark=0" to "watermark=1" and got:
> 
> [root@sandy ~]# perf test perf_event_attr
> 13: struct perf_event_attr setup                           :FAILED '/home/acme/libexec/perf-core/tests/attr/test-record-count' - match failure
>  FAILED!
> [root@sandy ~]#
> 
> But I wanted it to show _what_ didn't match, so I tried:
> 
> [root@sandy ~]# perf test -v perf_event_attr
> 13: struct perf_event_attr setup                           :
> --- start ---
> running '/home/acme/libexec/perf-core/tests/attr/test-record-count'
> FAILED '/home/acme/libexec/perf-core/tests/attr/test-record-count' - match failure
> ---- end ----
> struct perf_event_attr setup: FAILED!
> [root@sandy ~]#

yep, you'd need to run:
  python ./tests/attr.py -d ./tests/attr/ -p ./perf -t test-record-count -vvv

to see what really did not match

'perf test attr' takes just single -v option into account

could be changed ;)

> 
> Also is there a strict need for setting PERF_TEST_ATTR? I thought that if it
> found the /home/acme/libexec/perf-core/tests/attr/ dirs it would test it, but
> haven't dug deep, care to ellaborate here?

PERF_TEST_ATTR instructs perf to store each event details into PERF_TEST_ATTR directory

and python script is running 'PERF_TEST_ATTR=/tmp/temp perf ...' to get events


> 
> Ah, I just pushed perf/core with this patchset, thanks!

thanks,
jirka

  reply	other threads:[~2012-11-01 23:21 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 22:01 [PATCH 00/25] perf test: Add perf_event_attr tests Jiri Olsa
2012-10-30 22:01 ` [PATCH 01/25] perf tools: Remove BINDIR define from exec_cmd.o compilation Jiri Olsa
2012-11-14  6:36   ` [tip:perf/core] perf tools: Remove BINDIR define from exec_cmd. o compilation tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 02/25] perf tests: Move test objects into 'tests' directory Jiri Olsa
2012-11-02  1:48   ` Namhyung Kim
2012-11-02 10:30     ` Jiri Olsa
2012-11-14  6:39   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 03/25] perf tests: Add framework for automated perf_event_attr tests Jiri Olsa
2012-10-30 23:01   ` Jiri Olsa
2012-10-31 14:26     ` Arnaldo Carvalho de Melo
2012-10-31 14:52       ` [PATCHv2 " Jiri Olsa
2012-11-02  2:18         ` Namhyung Kim
2012-11-02 10:40           ` Jiri Olsa
2012-11-05 14:29             ` Arnaldo Carvalho de Melo
2012-11-05 14:41               ` Jiri Olsa
2012-11-14  6:40         ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 04/25] perf tests: Add attr record basic test Jiri Olsa
2012-11-14  6:52   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 05/25] perf tests: Add attr record group test Jiri Olsa
2012-11-14  6:54   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 06/25] perf tests: Add attr record event syntax " Jiri Olsa
2012-11-14  6:55   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 07/25] perf tests: Add attr record freq test Jiri Olsa
2012-11-14  6:56   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 08/25] perf tests: Add attr record count test Jiri Olsa
2012-11-14  6:57   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 09/25] perf tests: Add attr record graph test Jiri Olsa
2012-11-14  6:58   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 10/25] perf tests: Add attr record period test Jiri Olsa
2012-11-14  6:59   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 11/25] perf tests: Add attr record no samples test Jiri Olsa
2012-11-14  7:00   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 12/25] perf tests: Add attr record no-inherit test Jiri Olsa
2012-11-14  7:01   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 13/25] perf tests: Add attr record data test Jiri Olsa
2012-11-14  7:10   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 14/25] perf tests: Add attr record raw test Jiri Olsa
2012-11-14  7:11   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 15/25] perf tests: Add attr record no delay test Jiri Olsa
2012-11-14  7:12   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 16/25] perf tests: Add attr record branch any test Jiri Olsa
2012-11-14  7:13   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 17/25] perf tests: Add attr record branch filter tests Jiri Olsa
2012-11-14  7:14   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:01 ` [PATCH 18/25] perf tests: Add attr stat basic test Jiri Olsa
2012-10-30 22:02 ` [PATCH 19/25] perf tests: Add attr stat no-inherit test Jiri Olsa
2012-11-14  7:15   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:02 ` [PATCH 20/25] perf tests: Add attr stat group test Jiri Olsa
2012-11-14  7:16   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:02 ` [PATCH 21/25] perf tests: Add attr stat event syntax " Jiri Olsa
2012-11-14  7:18   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:02 ` [PATCH 22/25] perf tests: Add attr stat default test Jiri Olsa
2012-11-14  7:19   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:02 ` [PATCH 23/25] " Jiri Olsa
2012-11-14  7:20   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:02 ` [PATCH 24/25] perf tests: Add attr tests under builtin test command Jiri Olsa
2012-11-14  6:53   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-30 22:02 ` [PATCH 25/25] perf tests: Add documentation for attr tests Jiri Olsa
2012-11-14  7:21   ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-11-01 20:38 ` [PATCH 00/25] perf test: Add perf_event_attr tests Arnaldo Carvalho de Melo
2012-11-01 23:20   ` Jiri Olsa [this message]
2012-11-02  1:25     ` Namhyung Kim
2012-11-02  2:23       ` Namhyung Kim

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=20121101232055.GA1690@krava.redhat.com \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=cjashfor@linux.vnet.ibm.com \
    --cc=fweisbec@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.