From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/3] [4.0] arm/arm64: Do not group hardware events from different PMUs
Date: Thu, 19 Mar 2015 17:14:43 +0000 [thread overview]
Message-ID: <20150319171443.GA10153@leverpostej> (raw)
In-Reply-To: <1426616100-31628-1-git-send-email-suzuki.poulose@arm.com>
On Tue, Mar 17, 2015 at 06:14:57PM +0000, Suzuki K. Poulose wrote:
> From: "Suzuki K. Poulose" <suzuki.poulose@arm.com>
>
> This is a collection of fixes which denies grouping hardware events
> from different PMUs. They also fix crashes triggered by perf_fuzzer
> on Linux-4.0-rc2.
>
> This series hasn't changed since V1, except for better commit messages.
>
> Similar fixes are required in ARM-CCN PMU driver and is not straight forward
> as these changes.
>
> Suzuki K. Poulose (3):
> arm/pmu: Reject groups spanning multiple hardware PMUs
> arm64/pmu: Reject groups spanning multiple HW PMUs
> arm-cci: Reject groups spanning multiple HW PMUs
For the series:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
> arch/arm/kernel/perf_event.c | 21 +++++++++++++++------
> arch/arm64/kernel/perf_event.c | 21 +++++++++++++++------
> drivers/bus/arm-cci.c | 19 ++++++++++++++-----
> 3 files changed, 44 insertions(+), 17 deletions(-)
>
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2015-03-19 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 18:14 [PATCHv2 0/3] [4.0] arm/arm64: Do not group hardware events from different PMUs Suzuki K. Poulose
2015-03-17 18:14 ` [PATCH 1/3] arm/pmu: Reject groups spanning multiple hardware PMUs Suzuki K. Poulose
2015-03-17 18:14 ` [PATCH 2/3] arm64/pmu: Reject groups spanning multiple HW PMUs Suzuki K. Poulose
2015-03-17 18:15 ` [PATCH 3/3] arm-cci: " Suzuki K. Poulose
2015-03-18 17:18 ` [PATCHv2 0/3] [4.0] arm/arm64: Do not group hardware events from different PMUs Peter Zijlstra
2015-03-19 17:14 ` Mark Rutland [this message]
2015-03-24 15:54 ` Pawel Moll
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=20150319171443.GA10153@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).