From: Adrian Hunter <adrian.hunter@intel.com>
To: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
atrajeev@linux.vnet.ibm.com
Subject: Re: [PATCH v1] perf test: Add basic perf diff test
Date: Tue, 5 Dec 2023 07:44:17 +0200 [thread overview]
Message-ID: <ee68f32d-72a2-4e9f-aee1-7c195ad44765@intel.com> (raw)
In-Reply-To: <CAP-5=fWvADeeHVQObwk-eVNeOSC=eTTv2q8Rz4j3UtL5-6Getw@mail.gmail.com>
On 4/12/23 18:00, Ian Rogers wrote:
> On Mon, Nov 20, 2023 at 11:04 AM Ian Rogers <irogers@google.com> wrote:
>>
>> There are some old bug reports on perf diff crashing:
>> https://rhaas.blogspot.com/2012/06/perf-good-bad-ugly.html
>>
>> Happening across them I was prompted to add two very basic tests that
>> will give some perf diff coverage.
>>
>> Signed-off-by: Ian Rogers <irogers@google.com>
>
> Ping.
>
> Thanks,
> Ian
>
>> ---
>> tools/perf/tests/shell/diff.sh | 101 +++++++++++++++++++++++++++++++++
>> 1 file changed, 101 insertions(+)
>> create mode 100755 tools/perf/tests/shell/diff.sh
>>
>> diff --git a/tools/perf/tests/shell/diff.sh b/tools/perf/tests/shell/diff.sh
>> new file mode 100755
>> index 000000000000..213185763688
>> --- /dev/null
>> +++ b/tools/perf/tests/shell/diff.sh
>> @@ -0,0 +1,101 @@
>> +#!/bin/sh
>> +# perf diff tests
>> +# SPDX-License-Identifier: GPL-2.0
>> +
>> +set -e
>> +
>> +err=0
>> +perfdata1=$(mktemp /tmp/__perf_test.perf.data.XXXXX)
>> +perfdata2=$(mktemp /tmp/__perf_test.perf.data.XXXXX)
>> +perfdata3=$(mktemp /tmp/__perf_test.perf.data.XXXXX)
>> +testprog="perf test -w thloop"
>> +testsym="test_loop"
Could it benefit from skip_test_missing_symbol
>> +
>> +cleanup() {
>> + rm -rf "${perfdata1}"
>> + rm -rf "${perfdata1}".old
>> + rm -rf "${perfdata2}"
>> + rm -rf "${perfdata2}".old
>> + rm -rf "${perfdata3}"
>> + rm -rf "${perfdata3}".old
>> +
>> + trap - EXIT TERM INT
>> +}
>> +
>> +trap_cleanup() {
>> + cleanup
>> + exit 1
>> +}
>> +trap trap_cleanup EXIT TERM INT
>> +
>> +make_data() {
>> + file="$1"
>> + if ! perf record -o "${file}" ${testprog} 2> /dev/null
>> + then
>> + echo "Workload record [Failed record]"
>> + echo 1
>> + return
>> + fi
>> + if ! perf report -i "${file}" -q | grep -q "${testsym}"
>> + then
>> + echo "Workload record [Failed missing output]"
>> + echo 1
>> + return
>> + fi
>> + echo 0
>> +}
>> +
>> +test_two_files() {
>> + echo "Basic two file diff test"
>> + err=$(make_data "${perfdata1}")
>> + if [ $err != 0 ]
>> + then
>> + return
>> + fi
>> + err=$(make_data "${perfdata2}")
>> + if [ $err != 0 ]
>> + then
>> + return
>> + fi
>> +
>> + if ! perf diff "${perfdata1}" "${perfdata2}" | grep -q "${testsym}"
>> + then
>> + echo "Basic two file diff test [Failed diff]"
>> + err=1
>> + return
>> + fi
>> + echo "Basic two file diff test [Success]"
>> +}
>> +
>> +test_three_files() {
>> + echo "Basic three file diff test"
>> + err=$(make_data "${perfdata1}")
>> + if [ $err != 0 ]
>> + then
>> + return
>> + fi
>> + err=$(make_data "${perfdata2}")
>> + if [ $err != 0 ]
>> + then
>> + return
>> + fi
>> + err=$(make_data "${perfdata3}")
>> + if [ $err != 0 ]
>> + then
>> + return
>> + fi
>> +
>> + if ! perf diff "${perfdata1}" "${perfdata2}" "${perfdata3}" | grep -q "${testsym}"
>> + then
>> + echo "Basic three file diff test [Failed diff]"
>> + err=1
>> + return
>> + fi
>> + echo "Basic three file diff test [Success]"
>> +}
>> +
>> +test_two_files
>> +test_three_files
>> +
>> +cleanup
>> +exit $err
>> --
>> 2.43.0.rc1.413.gea7ed67945-goog
>>
next prev parent reply other threads:[~2023-12-05 5:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 19:04 [PATCH v1] perf test: Add basic perf diff test Ian Rogers
2023-12-04 16:00 ` Ian Rogers
2023-12-04 20:24 ` Arnaldo Carvalho de Melo
2023-12-05 5:44 ` Adrian Hunter [this message]
2023-12-05 16:52 ` Ian Rogers
2023-12-06 13:26 ` 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=ee68f32d-72a2-4e9f-aee1-7c195ad44765@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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.