From: jglauber@cavium.com (Jan Glauber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] Cavium ThunderX uncore PMU support
Date: Tue, 19 Apr 2016 12:35:10 +0200 [thread overview]
Message-ID: <20160419103510.GA5499@wintermute> (raw)
In-Reply-To: <CAEiAFz3eCsX3VoNus_Rq+En5zuB8fAxNCbC3ktw2NqLKwC=_kA@mail.gmail.com>
Mark,
are these patches still queued or should I repost them?
--Jan
On Mon, Apr 04, 2016 at 01:03:13PM +0200, Jan Glauber wrote:
> Hi Mark,
>
> can you have a look at these patches?
>
> Thanks,
> Jan
>
> 2016-03-09 17:21 GMT+01:00 Jan Glauber <jglauber@cavium.com>:
>
> This patch series provides access to various counters on the ThunderX SOC.
>
> For details of the uncore implementation see patch #1.
>
> Patches #2-5 add the various ThunderX specific PMUs.
>
> As suggested I've put the files under drivers/perf/uncore. I would
> prefer this location over drivers/bus because not all of the uncore
> drivers are bus related.
>
> Changes to v1:
> - Added NUMA support
> - Fixed CPU hotplug by pmu migration
> - Moved files to drivers/perf/uncore
> - Removed OCX FRC and LNE drivers, these will fit better into a edac driver
> - improved comments abount overflow interrupts
> - removed max device limit
> - trimmed include files
>
> Feedback welcome!
> Jan
>
> -------------------------------------------------
>
> Jan Glauber (5):
> ? arm64/perf: Basic uncore counter support for Cavium ThunderX
> ? arm64/perf: Cavium ThunderX L2C TAD uncore support
> ? arm64/perf: Cavium ThunderX L2C CBC uncore support
> ? arm64/perf: Cavium ThunderX LMC uncore support
> ? arm64/perf: Cavium ThunderX OCX TLK uncore support
>
> ?drivers/perf/Makefile? ? ? ? ? ? ? ? ? ? ? ?|? ?1 +
> ?drivers/perf/uncore/Makefile? ? ? ? ? ? ? ? |? ?5 +
> ?drivers/perf/uncore/uncore_cavium.c? ? ? ? ?| 314 +++++++++++++++
> ?drivers/perf/uncore/uncore_cavium.h? ? ? ? ?|? 95 +++++
> ?drivers/perf/uncore/uncore_cavium_l2c_cbc.c | 237 +++++++++++
> ?drivers/perf/uncore/uncore_cavium_l2c_tad.c | 600
> ++++++++++++++++++++++++++++
> ?drivers/perf/uncore/uncore_cavium_lmc.c? ? ?| 196 +++++++++
> ?drivers/perf/uncore/uncore_cavium_ocx_tlk.c | 380 ++++++++++++++++++
> ?8 files changed, 1828 insertions(+)
> ?create mode 100644 drivers/perf/uncore/Makefile
> ?create mode 100644 drivers/perf/uncore/uncore_cavium.c
> ?create mode 100644 drivers/perf/uncore/uncore_cavium.h
> ?create mode 100644 drivers/perf/uncore/uncore_cavium_l2c_cbc.c
> ?create mode 100644 drivers/perf/uncore/uncore_cavium_l2c_tad.c
> ?create mode 100644 drivers/perf/uncore/uncore_cavium_lmc.c
> ?create mode 100644 drivers/perf/uncore/uncore_cavium_ocx_tlk.c
>
> --
> 1.9.1
>
>
>
next prev parent reply other threads:[~2016-04-19 10:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 16:21 [PATCH v2 0/5] Cavium ThunderX uncore PMU support Jan Glauber
2016-03-09 16:21 ` [PATCH v2 1/5] arm64/perf: Basic uncore counter support for Cavium ThunderX Jan Glauber
2016-04-19 15:06 ` Mark Rutland
2016-04-20 12:29 ` Jan Glauber
2016-03-09 16:21 ` [PATCH v2 2/5] arm64/perf: Cavium ThunderX L2C TAD uncore support Jan Glauber
2016-04-19 15:43 ` Mark Rutland
2016-03-09 16:21 ` [PATCH v2 3/5] arm64/perf: Cavium ThunderX L2C CBC " Jan Glauber
2016-04-19 15:56 ` Mark Rutland
2016-03-09 16:21 ` [PATCH v2 4/5] arm64/perf: Cavium ThunderX LMC " Jan Glauber
2016-03-09 16:21 ` [PATCH v2 5/5] arm64/perf: Cavium ThunderX OCX TLK " Jan Glauber
2016-04-04 12:19 ` [PATCH v2 0/5] Cavium ThunderX uncore PMU support Jan Glauber
2016-04-25 11:22 ` Will Deacon
2016-04-25 12:02 ` Jan Glauber
2016-04-25 13:19 ` Will Deacon
2016-04-26 12:08 ` Jan Glauber
2016-04-26 13:53 ` Will Deacon
2016-04-27 10:51 ` Jan Glauber
2016-04-27 11:18 ` Mark Rutland
[not found] ` <CAEiAFz3eCsX3VoNus_Rq+En5zuB8fAxNCbC3ktw2NqLKwC=_kA@mail.gmail.com>
2016-04-19 10:35 ` Jan Glauber [this message]
2016-04-19 16:03 ` Mark Rutland
2016-06-28 10:24 ` Will Deacon
2016-06-28 14:04 ` Jan Glauber
2016-07-04 10:11 ` Will Deacon
2016-09-16 7:55 ` Will Deacon
2016-09-16 8:39 ` Jan Glauber
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=20160419103510.GA5499@wintermute \
--to=jglauber@cavium.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