From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, jolsa@kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] perf test: Ignore .scale and other special files
Date: Mon, 6 Jun 2016 11:51:48 -0300 [thread overview]
Message-ID: <20160606145148.GC31477@kernel.org> (raw)
In-Reply-To: <1465223766-29902-1-git-send-email-andi@firstfloor.org>
Em Mon, Jun 06, 2016 at 07:36:06AM -0700, Andi Kleen escreveu:
> perf test tries to parse all entries in /sys/devices/cpu/events/.
> Ignore the special entries like '.scale', which cannot be directly
> parsed as an event. This patch assumes all files containing a '.'
> are special and can be ignored.
> +++ b/tools/perf/tests/parse-events.c
> @@ -1783,8 +1783,8 @@ static int test_pmu_events(void)
> - if (!strcmp(ent->d_name, ".") ||
> - !strcmp(ent->d_name, ".."))
> + /* Names containing . are special and cannot be used directly */
> + if (strchr(ent->d_name, '.'))
> continue;
Ok, this is a more generic fix than the one I used here (adding: ||
strends(ent->d_name, ".scale"), I'll use yours, but this gets us to the
following error:
[root@jouet ~]# perf test -v 5 2>&1 | tail
running test 49 'r1234/name=rawpmu/'
running test 50 '4:0x6530160/name=numpmu/'
running test 51 'L1-dcache-misses/name=cachepmu/'
running test 0 'cpu/config=10,config1,config2=3,period=1000/u'
running test 1 'cpu/config=1,name=krava/u,cpu/config=2/u'
running test 2 'cpu/config=1,call-graph=fp,time,period=100000/,cpu/config=2,call-graph=no,time=0,period=2000/'
failed to parse event 'topdown-total-slots:u,cpu/event=topdown-total-slots/u', err 1
test child finished with 1
---- end ----
parse events tests: FAILED!
[root@jouet ~]# cat /sys/devices/cpu/events/topdown-total-slots
event=0x3c,umask=0x0,any=1[root@jouet ~]#
[root@jouet ~]#
[root@jouet ~]# cat /sys/devices/cpu/events/bus-cycles
event=0x3c,umask=0x01
[root@jouet ~]#
I.e seems to be bickering about a missing newline in the sysfs entry, will check the parser...
- Arnaldo
next prev parent reply other threads:[~2016-06-06 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 14:36 [PATCH] perf test: Ignore .scale and other special files Andi Kleen
2016-06-06 14:51 ` Arnaldo Carvalho de Melo [this message]
2016-06-06 14:54 ` Arnaldo Carvalho de Melo
2016-06-06 15:09 ` Arnaldo Carvalho de Melo
2016-06-06 16:31 ` Andi Kleen
2016-06-06 19:56 ` Arnaldo Carvalho de Melo
2016-06-08 8:38 ` [tip:perf/core] " tip-bot for Andi Kleen
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=20160606145148.GC31477@kernel.org \
--to=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.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