From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/7] Cavium ThunderX uncore PMU support
Date: Fri, 12 Feb 2016 17:00:57 +0000 [thread overview]
Message-ID: <20160212170056.GC20262@leverpostej> (raw)
In-Reply-To: <cover.1455295032.git.jglauber@cavium.com>
On Fri, Feb 12, 2016 at 05:55:05PM +0100, Jan Glauber wrote:
> Hi,
>
> this patch series provides access to various counters on the ThunderX SOC.
>
> For details of the implementation see patch #1.
>
> Patches #2-7 add ther various ThunderX specific PMUs.
>
> I did not want to put these file into arch/arm64/kernel so I added a
> "uncore" directory. Maybe this should be put somewhere under drivers/
> instead.
This is probably better suited to drivers/perf/, or drivers/bus/ (where
CCN and CCI perf drivers live).
Mark.
prev parent reply other threads:[~2016-02-12 17:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 16:55 [RFC PATCH 0/7] Cavium ThunderX uncore PMU support Jan Glauber
2016-02-12 16:55 ` [RFC PATCH 1/7] arm64/perf: Basic uncore counter support for Cavium ThunderX Jan Glauber
2016-02-12 17:36 ` Mark Rutland
2016-02-13 1:47 ` David Daney
2016-02-15 11:33 ` Mark Rutland
2016-02-15 14:07 ` Jan Glauber
2016-02-15 14:27 ` Mark Rutland
2016-02-15 14:46 ` Mark Rutland
2016-02-15 15:34 ` Jan Glauber
2016-02-16 8:41 ` Jan Glauber
2016-03-11 10:54 ` Jan Glauber
2016-02-12 16:55 ` [RFC PATCH 2/7] arm64/perf: Cavium ThunderX L2C TAD uncore support Jan Glauber
2016-02-12 16:55 ` [RFC PATCH 3/7] arm64/perf: Cavium ThunderX L2C CBC " Jan Glauber
2016-02-12 16:55 ` [RFC PATCH 4/7] arm64/perf: Cavium ThunderX LMC " Jan Glauber
2016-02-12 16:55 ` [RFC PATCH 5/7] arm64/perf: Cavium ThunderX OCX LNE " Jan Glauber
2016-02-12 16:55 ` [RFC PATCH 6/7] arm64/perf: Cavium ThunderX OCX FRC " Jan Glauber
2016-02-12 16:55 ` [RFC PATCH 7/7] arm64/perf: Cavium ThunderX OCX TLK " Jan Glauber
2016-02-12 17:00 ` Mark Rutland [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=20160212170056.GC20262@leverpostej \
--to=mark.rutland@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).