From: German Gomez <german.gomez@arm.com>
To: Thomas Richter <tmricht@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
acme@kernel.org, james.clark@arm.com
Cc: svens@linux.ibm.com, gor@linux.ibm.com, sumanthk@linux.ibm.com,
hca@linux.ibm.com, Namhyung Kim <namhyung@kernel.org>,
Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH] perf/tests: Fix test case 95 on s390 and use same event
Date: Thu, 28 Jul 2022 13:28:51 +0100 [thread overview]
Message-ID: <3cb2c002-e4e3-c7b4-148d-5e2d0c406b84@arm.com> (raw)
In-Reply-To: <550e7e9f-19cb-0b1f-fd3e-f0d958b4e75b@linux.ibm.com>
On 28/07/2022 13:20, Thomas Richter wrote:
> On 7/28/22 11:25, German Gomez wrote:
>> Thanks for the fix, Thomas
>>
>> On 27/07/2022 15:14, Thomas Richter wrote:
>>> On linux-next tree perf test 95 was added recently.
>>> s390 does not support branch sampling at all and the test case fails
>>> despite for checking branch support before hand.
>>> The check for support of branching
>>> uses the software event named dummy, as seen in the line:
>>>
>>> perf record -b -o- -e dummy -B true > /dev/null 2>&1 || exit 2
>> Just curious, do you know why the command succeeds in this platform (and
>> potentially others)?
>>
>> I got the idea of using "dummy" from [1] but only tested on arm64 and
>> x86. I thought the platforms would reject it if -b was not implemented
>> regardless of the event. Did I misunderstand the use of dummy?
>>
>> Thanks,
>> German
>>
>> [1] https://lore.kernel.org/all/20220617073840.GA45710@leoy-ThinkPad-X240s/
>>
> Well, dummy is a predefined event of type software, you see that when you add
> some -v options as in
> # perf record -e dummy -vvv
> DEBUGINFOD_URLS=
> Using CPUID IBM,3931,704,A01,3.7,002f
> nr_cblocks: 0
> affinity: SYS
> mmap flush: 1
> comp level: 0
> ------------------------------------------------------------
> perf_event_attr:
> type 1 <----------- type 1 is software
> size 128
> config 0x9
> { sample_period, sample_freq } 4000
>
>
> So this event is never sent to an hardware PMU (which would have type 0) and thus
> mostly succeeds where as the perf record command without event uses default
> event cycles. And that one is sent to hardware PMU on s390...
Thanks for explaining! My bad for missing this.
Acked-by: German Gomez <german.gomez@arm.com>
>
prev parent reply other threads:[~2022-07-28 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 14:14 Thomas Richter
2022-07-28 9:09 ` James Clark
2022-07-28 9:25 ` German Gomez
2022-07-28 12:20 ` Thomas Richter
2022-07-28 12:28 ` German Gomez [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=3cb2c002-e4e3-c7b4-148d-5e2d0c406b84@arm.com \
--to=german.gomez@arm.com \
--cc=acme@kernel.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sumanthk@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=tmricht@linux.ibm.com \
/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
all inboxes | Powered by JetHome®