From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Ian Rogers <irogers@google.com>
Cc: acme@kernel.org, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, peterz@infradead.org,
mingo@redhat.com, jolsa@kernel.org, namhyung@kernel.org,
adrian.hunter@intel.com, tinghao.zhang@intel.com
Subject: Re: [PATCH] perf test: Basic branch counter support
Date: Tue, 7 Nov 2023 13:36:37 -0500 [thread overview]
Message-ID: <eff62fd6-10f4-4548-8fab-c6c56338be66@linux.intel.com> (raw)
In-Reply-To: <CAP-5=fWjXS43xBujQ2DOAeo41WX5L4hfTfJVEV8h6i1Uu2HBEA@mail.gmail.com>
On 2023-11-07 1:05 p.m., Ian Rogers wrote:
> On Tue, Nov 7, 2023 at 9:44 AM <kan.liang@linux.intel.com> wrote:
>>
>> From: Kan Liang <kan.liang@linux.intel.com>
>>
>> Add a basic test for the branch counter feature.
>>
>> The test verifies that
>> - The new filter can be successfully applied on the supported platforms.
>> - The counter value can be outputted via the perf report -D
>>
>> Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
>
> Thanks Kan!
>
>> ---
>> tools/perf/tests/shell/record.sh | 30 ++++++++++++++++++++++++++++++
>> 1 file changed, 30 insertions(+)
>>
>> diff --git a/tools/perf/tests/shell/record.sh b/tools/perf/tests/shell/record.sh
>> index 4fbc74805d52..2783e867c07c 100755
>> --- a/tools/perf/tests/shell/record.sh
>> +++ b/tools/perf/tests/shell/record.sh
>> @@ -11,6 +11,9 @@ err=0
>> perfdata=$(mktemp /tmp/__perf_test.perf.data.XXXXX)
>> testprog="perf test -w thloop"
>> testsym="test_loop"
>> +cpu_pmu_dir="/sys/bus/event_source/devices/cpu*"
>> +br_cntr_file="/caps/branch_counter_nr"
>> +br_cntr_output="branch stack counters"
>>
>> cleanup() {
>> rm -rf "${perfdata}"
>> @@ -154,10 +157,37 @@ test_workload() {
>> echo "Basic target workload test [Success]"
>> }
>>
>> +test_branch_counter() {
>> + echo "Basic branch counter test"
>> + # Check if the branch counter feature is supported
>
> If $cpu_pmu_dir is empty, e.g. ARM and S390, this should also skip.
>
Yes, I've tested with a fake unsupported dir. The test case is skipped
as well.
>> + for dir in $cpu_pmu_dir
>> + do
>> + if [ ! -e "$dir$br_cntr_file" ]
>> + then
>> + echo "Not support branch counter feature [Skipped]"
>
> Perhaps here it'd be clearer to output:
> echo "branch counter feature not supported on all core PMUs ($dir) [Skipped]"
>
Sure, I will change it in V2.
Thanks,
Kan
> Thanks,
> Ian
>
>> + return
>> + fi
>> + done
>> + if ! perf record -o "${perfdata}" -j any,counter ${testprog} 2> /dev/null
>> + then
>> + echo "Basic branch counter test [Failed record]"
>> + err=1
>> + return
>> + fi
>> + if ! perf report -i "${perfdata}" -D -q | grep -q "$br_cntr_output"
>> + then
>> + echo "Basic branch record test [Failed missing output]"
>> + err=1
>> + return
>> + fi
>> + echo "Basic branch counter test [Success]"
>> +}
>> +
>> test_per_thread
>> test_register_capture
>> test_system_wide
>> test_workload
>> +test_branch_counter
>>
>> cleanup
>> exit $err
>> --
>> 2.35.1
>>
>
prev parent reply other threads:[~2023-11-07 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 17:44 [PATCH] perf test: Basic branch counter support kan.liang
2023-11-07 18:05 ` Ian Rogers
2023-11-07 18:36 ` Liang, Kan [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=eff62fd6-10f4-4548-8fab-c6c56338be66@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tinghao.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).