From: "Liang, Kan" <kan.liang@linux.intel.com>
To: acme@kernel.org, irogers@google.com,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Cc: peterz@infradead.org, mingo@redhat.com, jolsa@kernel.org,
namhyung@kernel.org, adrian.hunter@intel.com,
tinghao.zhang@intel.com
Subject: Re: [PATCH V2] perf test: Basic branch counter support
Date: Mon, 13 Nov 2023 11:11:43 -0500 [thread overview]
Message-ID: <85aac482-2318-4fb5-be8a-b6d17e19407b@linux.intel.com> (raw)
In-Reply-To: <20231107184020.1497571-1-kan.liang@linux.intel.com>
Hi Ian,
On 2023-11-07 1:40 p.m., 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>
> ---
>
> Changes since V2:
> - Update the output msg for the skipped case (Ian)
>
Any comments for this patch?
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..cc207a16ae24 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
> + for dir in $cpu_pmu_dir
> + do
> + if [ ! -e "$dir$br_cntr_file" ]
> + then
> + echo "branch counter feature not supported on all core PMUs ($dir) [Skipped]"
> + 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
next prev parent reply other threads:[~2023-11-13 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 18:40 [PATCH V2] perf test: Basic branch counter support kan.liang
2023-11-13 16:11 ` Liang, Kan [this message]
2023-11-21 0:22 ` Ian Rogers
2023-11-22 11:56 ` Arnaldo Carvalho de Melo
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=85aac482-2318-4fb5-be8a-b6d17e19407b@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 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.