From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm-cci: ensure perf synchronisation
Date: Mon, 4 Jul 2016 11:22:05 +0100 [thread overview]
Message-ID: <20160704102205.GD1639@arm.com> (raw)
In-Reply-To: <1467136218-15789-3-git-send-email-mark.rutland@arm.com>
On Tue, Jun 28, 2016 at 06:50:18PM +0100, Mark Rutland wrote:
> Currently the IRQ core is permitted to make the CCI PMU IRQ handler
> threaded, and will allow userspace to change the CPU affinity of the
> interrupt behind our back. Both of these could violate our
> synchronisation requirements with the core perf code, which relies upon
> strict CPU affinity and disabling of interrupts to guarantee mutual
> exclusion in some cases.
Minor nit, but I think $subject is particularly unhelpful for these two
patches. How about "arm-ccX: fix PMU interrupt flags"?
> As with the CPU PMU drivers, we should request the interrupt with
> IRQF_NOBALANCING and IRQF_NO_THREAD, to avoid these issues.
>
> Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Punit Agrawal <punit.agrawal@arm.com>
> Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Olof Johansson <olof@lixom.net>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: <arm@kernel.org>
> ---
> drivers/bus/arm-cci.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/bus/arm-cci.c b/drivers/bus/arm-cci.c
> index a49b283..6a8825a 100644
> --- a/drivers/bus/arm-cci.c
> +++ b/drivers/bus/arm-cci.c
> @@ -881,7 +881,8 @@ static int pmu_request_irq(struct cci_pmu *cci_pmu, irq_handler_t handler)
> * This should allow handling of non-unique interrupt for the counters.
> */
> for (i = 0; i < cci_pmu->nr_irqs; i++) {
> - int err = request_irq(cci_pmu->irqs[i], handler, IRQF_SHARED,
Why is this shared and who is the line shared with? We should check that
we don't have contradictory IRQ flags in the other irq request path(s).
Will
next prev parent reply other threads:[~2016-07-04 10:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 17:50 [PATCH 0/2] arm-cc*: ensure perf synchronisation Mark Rutland
2016-06-28 17:50 ` [PATCH 1/2] arm-ccn: " Mark Rutland
2016-07-04 13:39 ` Pawel Moll
2016-07-04 13:50 ` Mark Rutland
2016-06-28 17:50 ` [PATCH 2/2] arm-cci: " Mark Rutland
2016-07-04 10:22 ` Will Deacon [this message]
2016-07-04 10:31 ` Mark Rutland
2016-07-04 10:44 ` Mark Rutland
2016-07-04 11:16 ` Punit Agrawal
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=20160704102205.GD1639@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).