From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Thomas Richter <tmricht@linux.ibm.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Riccardo Mancini <rickyman7@gmail.com>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf test: Test 2 libpfm4 error cases
Date: Thu, 27 May 2021 13:26:51 -0300 [thread overview]
Message-ID: <YK/IS9cQeSuZT4cK@kernel.org> (raw)
In-Reply-To: <CAP-5=fXpibzr2Vdzy4RHPVzQbSAOLimpHeuVY_L_YsXDy-2_1Q@mail.gmail.com>
Em Thu, May 27, 2021 at 08:52:14AM -0700, Ian Rogers escreveu:
> On Wed, May 19, 2021 at 8:12 AM Ian Rogers <irogers@google.com> wrote:
> >
> > Proposed in:
> > https://lore.kernel.org/lkml/20210517140931.2559364-1-tmricht@linux.ibm.com/
> >
> > Signed-off-by: Ian Rogers <irogers@google.com>
>
> Ping.
Thanks, applied.
- Arnaldo
> Thanks!
> Ian
>
> > ---
> > tools/perf/tests/pfm.c | 10 ++++++++++
> > 1 file changed, 10 insertions(+)
> >
> > diff --git a/tools/perf/tests/pfm.c b/tools/perf/tests/pfm.c
> > index d4b0ef74defc..acd50944f6af 100644
> > --- a/tools/perf/tests/pfm.c
> > +++ b/tools/perf/tests/pfm.c
> > @@ -155,6 +155,16 @@ static int test__pfm_group(void)
> > .nr_events = 3,
> > .nr_groups = 1,
> > },
> > + {
> > + .events = "instructions}",
> > + .nr_events = 1,
> > + .nr_groups = 0,
> > + },
> > + {
> > + .events = "{{instructions}}",
> > + .nr_events = 0,
> > + .nr_groups = 0,
> > + },
> > };
> >
> > for (i = 0; i < ARRAY_SIZE(table); i++) {
> > --
> > 2.31.1.751.gd2f1c929bd-goog
> >
--
- Arnaldo
prev parent reply other threads:[~2021-05-27 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 15:12 [PATCH] perf test: Test 2 libpfm4 error cases Ian Rogers
2021-05-27 15:52 ` Ian Rogers
2021-05-27 16:26 ` 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=YK/IS9cQeSuZT4cK@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--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 \
--cc=rickyman7@gmail.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;
as well as URLs for NNTP newsgroup(s).