From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@arm.com>
Cc: German Gomez <german.gomez@arm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH] perf test: Add perf_event_attr tests for the arm_spe event
Date: Sat, 5 Mar 2022 16:00:39 -0300 [thread overview]
Message-ID: <YiOzV7cUbWDNNMdH@kernel.org> (raw)
In-Reply-To: <fb98e7fd-bf0f-bc3b-ad2a-2775d2ef321d@arm.com>
Em Mon, Feb 28, 2022 at 03:05:21PM +0000, James Clark escreveu:
>
>
> On 26/01/2022 16:07, German Gomez wrote:
> > Adds a couple of perf_event_attr tests for the fix introduced in [1].
> > The tests check that the correct sample_period value is set in the
> > struct perf_event_attr of the arm_spe events.
> >
> > [1]: https://lore.kernel.org/all/20220118144054.2541-1-german.gomez@arm.com/
> >
> > Signed-off-by: German Gomez <german.gomez@arm.com>
>
> Reviewed-by: James Clark <james.clark@arm.com>
Thanks, applied.
- Arnaldo
> > ---
> > tools/perf/tests/attr/README | 2 +
> > tools/perf/tests/attr/base-record-spe | 40 +++++++++++++++++++
> > tools/perf/tests/attr/test-record-spe-period | 12 ++++++
> > .../tests/attr/test-record-spe-period-term | 12 ++++++
> > 4 files changed, 66 insertions(+)
> > create mode 100644 tools/perf/tests/attr/base-record-spe
> > create mode 100644 tools/perf/tests/attr/test-record-spe-period
> > create mode 100644 tools/perf/tests/attr/test-record-spe-period-term
> >
> > diff --git a/tools/perf/tests/attr/README b/tools/perf/tests/attr/README
> > index 1116fc6bf2ac..454505d343fa 100644
> > --- a/tools/perf/tests/attr/README
> > +++ b/tools/perf/tests/attr/README
> > @@ -58,6 +58,8 @@ Following tests are defined (with perf commands):
> > perf record -c 100 -P kill (test-record-period)
> > perf record -c 1 --pfm-events=cycles:period=2 (test-record-pfm-period)
> > perf record -R kill (test-record-raw)
> > + perf record -c 2 -e arm_spe_0// -- kill (test-record-spe-period)
> > + perf record -e arm_spe_0/period=3/ -- kill (test-record-spe-period-term)
> > perf stat -e cycles kill (test-stat-basic)
> > perf stat kill (test-stat-default)
> > perf stat -d kill (test-stat-detailed-1)
> > diff --git a/tools/perf/tests/attr/base-record-spe b/tools/perf/tests/attr/base-record-spe
> > new file mode 100644
> > index 000000000000..08fa96b59240
> > --- /dev/null
> > +++ b/tools/perf/tests/attr/base-record-spe
> > @@ -0,0 +1,40 @@
> > +[event]
> > +fd=*
> > +group_fd=-1
> > +flags=*
> > +cpu=*
> > +type=*
> > +size=*
> > +config=*
> > +sample_period=*
> > +sample_type=*
> > +read_format=*
> > +disabled=*
> > +inherit=*
> > +pinned=*
> > +exclusive=*
> > +exclude_user=*
> > +exclude_kernel=*
> > +exclude_hv=*
> > +exclude_idle=*
> > +mmap=*
> > +comm=*
> > +freq=*
> > +inherit_stat=*
> > +enable_on_exec=*
> > +task=*
> > +watermark=*
> > +precise_ip=*
> > +mmap_data=*
> > +sample_id_all=*
> > +exclude_host=*
> > +exclude_guest=*
> > +exclude_callchain_kernel=*
> > +exclude_callchain_user=*
> > +wakeup_events=*
> > +bp_type=*
> > +config1=*
> > +config2=*
> > +branch_sample_type=*
> > +sample_regs_user=*
> > +sample_stack_user=*
> > diff --git a/tools/perf/tests/attr/test-record-spe-period b/tools/perf/tests/attr/test-record-spe-period
> > new file mode 100644
> > index 000000000000..75f8c9cd8e3f
> > --- /dev/null
> > +++ b/tools/perf/tests/attr/test-record-spe-period
> > @@ -0,0 +1,12 @@
> > +[config]
> > +command = record
> > +args = --no-bpf-event -c 2 -e arm_spe_0// -- kill >/dev/null 2>&1
> > +ret = 1
> > +arch = aarch64
> > +
> > +[event-10:base-record-spe]
> > +sample_period=2
> > +freq=0
> > +
> > +# dummy event
> > +[event-1:base-record-spe]
> > diff --git a/tools/perf/tests/attr/test-record-spe-period-term b/tools/perf/tests/attr/test-record-spe-period-term
> > new file mode 100644
> > index 000000000000..8f60a4fec657
> > --- /dev/null
> > +++ b/tools/perf/tests/attr/test-record-spe-period-term
> > @@ -0,0 +1,12 @@
> > +[config]
> > +command = record
> > +args = --no-bpf-event -e arm_spe_0/period=3/ -- kill >/dev/null 2>&1
> > +ret = 1
> > +arch = aarch64
> > +
> > +[event-10:base-record-spe]
> > +sample_period=3
> > +freq=0
> > +
> > +# dummy event
> > +[event-1:base-record-spe]
--
- Arnaldo
prev parent reply other threads:[~2022-03-05 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 16:07 [PATCH] perf test: Add perf_event_attr tests for the arm_spe event German Gomez
2022-02-05 8:10 ` Leo Yan
2022-02-07 10:50 ` German Gomez
2022-02-07 11:03 ` Leo Yan
2022-02-28 11:56 ` German Gomez
2022-02-28 15:05 ` James Clark
2022-03-05 19:00 ` Arnaldo Carvalho de Melo [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=YiOzV7cUbWDNNMdH@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=german.gomez@arm.com \
--cc=james.clark@arm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@redhat.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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).