From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 0/4] Add support for ThunderX2 pmu events using json files
Date: Thu, 12 Oct 2017 16:24:02 +0100 [thread overview]
Message-ID: <20171012152402.GC5614@arm.com> (raw)
In-Reply-To: <20171012141116.32475-1-ganapatrao.kulkarni@cavium.com>
On Thu, Oct 12, 2017 at 07:41:12PM +0530, Ganapatrao Kulkarni wrote:
> Extending json/jevent framework for parsing arm64 event files.
> Adding jevents for ThunderX2 implementation defined PMU events.
>
> v8:
> - Rename thunderx2 directory to cavium
For the series:
Acked-by: Will Deacon <will.deacon@arm.com>
Although note that this conflicts against a queued fix from Mark[1], so
you'll need to rebase on top of that.
Will
[1] https://patchwork.kernel.org/patch/9990237/
next prev parent reply other threads:[~2017-10-12 15:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 14:11 [PATCH v8 0/4] Add support for ThunderX2 pmu events using json files Ganapatrao Kulkarni
2017-10-12 14:11 ` [PATCH v8 1/4] perf utils: passing pmu as a parameter to function get_cpuid_str Ganapatrao Kulkarni
2017-10-12 14:11 ` [PATCH v8 2/4] perf tools arm64: Add support for get_cpuid_str function Ganapatrao Kulkarni
2017-10-12 14:11 ` [PATCH v8 3/4] perf utils: Add helper function is_pmu_core to detect PMU CORE devices Ganapatrao Kulkarni
2017-10-12 14:11 ` [PATCH v8 4/4] perf vendor events arm64: Add ThunderX2 implementation defined pmu core events Ganapatrao Kulkarni
2017-10-12 15:24 ` Will Deacon [this message]
2017-10-12 17:24 ` [PATCH v8 0/4] Add support for ThunderX2 pmu events using json files Ganapatrao Kulkarni
2017-10-13 9:11 ` Will Deacon
2017-10-13 13:04 ` Arnaldo Carvalho de Melo
2017-10-13 19:33 ` 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=20171012152402.GC5614@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.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 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).