From: rric@kernel.org (Robert Richter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 0/4] Add support for ThunderX2 pmu events using json files
Date: Thu, 12 Oct 2017 12:38:20 +0200 [thread overview]
Message-ID: <20171012103820.GC17924@rric.localdomain> (raw)
In-Reply-To: <20171012103419.29824-1-ganapatrao.kulkarni@cavium.com>
On 12.10.17 16:04:15, Ganapatrao Kulkarni wrote:
> tools/perf/arch/arm64/util/Build | 1 +
> tools/perf/arch/arm64/util/header.c | 65 ++++++++++++++++++++++
> tools/perf/arch/powerpc/util/header.c | 2 +-
> tools/perf/arch/x86/util/header.c | 2 +-
> tools/perf/pmu-events/arch/arm64/mapfile.csv | 15 +++++
> .../arch/arm64/thunderx2/thunderx2-imp-def.json | 62 +++++++++++++++++++++
I guess the dir needs to be named 'cavium'.
-Robert
> tools/perf/util/header.h | 3 +-
> tools/perf/util/pmu.c | 52 +++++++++++++----
> 8 files changed, 189 insertions(+), 13 deletions(-)
next prev parent reply other threads:[~2017-10-12 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 10:34 [PATCH v7 0/4] Add support for ThunderX2 pmu events using json files Ganapatrao Kulkarni
2017-10-12 10:34 ` [PATCH v7 1/4] perf utils: passing pmu as a parameter to function get_cpuid_str Ganapatrao Kulkarni
2017-10-12 10:34 ` [PATCH v7 2/4] perf tools arm64: Add support for get_cpuid_str function Ganapatrao Kulkarni
2017-10-12 10:34 ` [PATCH v7 3/4] perf utils: Add helper function is_pmu_core to detect PMU CORE devices Ganapatrao Kulkarni
2017-10-12 10:34 ` [PATCH v7 4/4] perf vendor events arm64: Add ThunderX2 implementation defined pmu core events Ganapatrao Kulkarni
2017-10-12 10:38 ` Robert Richter [this message]
2017-10-12 10:50 ` [PATCH v7 0/4] Add support for ThunderX2 pmu events using json files Ganapatrao Kulkarni
2017-10-12 10:58 ` Will Deacon
2017-10-12 11:45 ` Zhangshaokun
2017-10-12 13:47 ` Ganapatrao Kulkarni
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=20171012103820.GC17924@rric.localdomain \
--to=rric@kernel.org \
--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