From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: John Garry <john.garry@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, kjain@linux.ibm.com, irogers@google.com,
yao.jin@linux.intel.com, yeyunfeng@huawei.com,
linux-kernel@vger.kernel.org, linuxarm@huawei.com
Subject: Re: [PATCH v2 0/2] perf PMU events test: Add scenario for arch std events
Date: Tue, 27 Oct 2020 13:34:30 -0300 [thread overview]
Message-ID: <20201027163430.GJ2479604@kernel.org> (raw)
In-Reply-To: <1603364547-197086-1-git-send-email-john.garry@huawei.com>
Em Thu, Oct 22, 2020 at 07:02:25PM +0800, John Garry escreveu:
> The small series covers the following:
> - Tidy error handling in jevents a bit
> - Expands on PMU events test to cover jevents arch std events support
>
> Differences to v1:
> - Revert to original logic in jevents.c error path
Thanks, applied both together with Kajol's Reviewed-by tags.
- Arnaldo
> John Garry (2):
> perf jevents: Tidy error handling
> perf jevents: Add test for arch std events
>
> .../pmu-events/arch/test/arch-std-events.json | 8 ++
> .../pmu-events/arch/test/test_cpu/cache.json | 5 ++
> tools/perf/pmu-events/jevents.c | 87 +++++++++----------
> tools/perf/tests/pmu-events.c | 14 +++
> 4 files changed, 66 insertions(+), 48 deletions(-)
> create mode 100644 tools/perf/pmu-events/arch/test/arch-std-events.json
> create mode 100644 tools/perf/pmu-events/arch/test/test_cpu/cache.json
>
> --
> 2.26.2
>
--
- Arnaldo
prev parent reply other threads:[~2020-10-27 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 11:02 [PATCH v2 0/2] perf PMU events test: Add scenario for arch std events John Garry
2020-10-22 11:02 ` [PATCH v2 1/2] perf jevents: Tidy error handling John Garry
2020-10-23 7:49 ` kajoljain
2020-10-22 11:02 ` [PATCH v2 2/2] perf jevents: Add test for arch std events John Garry
2020-10-23 7:57 ` kajoljain
2020-10-27 16:34 ` 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=20201027163430.GJ2479604@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yao.jin@linux.intel.com \
--cc=yeyunfeng@huawei.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.