linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] drivers/perf: arm_pmu: rework IRQ management
Date: Mon, 30 Jan 2017 15:31:16 +0000	[thread overview]
Message-ID: <1485790279-3139-1-git-send-email-mark.rutland@arm.com> (raw)

For historical reasons, we lazily request and free interrupts in the
arm_pmu driver, managing affinity at request time. Unfortunately, this
is not well balanced w.r.t. CPU hotplug, resulting in a number of
issues.

This series addresses this by reworking the way we manage interrupts,
splitting request/free from affinity management. This renders some code
redundant, and said code is removed.

I've given this a spin on a Juno R1 system and another system which uses PPIs.
I've verified that the IRQ affinity is as expected after CPUs are brought
online. I've also run basic perf queries and the perf fuzzer, both in parallel
with random hotplug events.

Thanks,
Mark.

Mark Rutland (3):
  drivers/perf: arm_pmu: rework per-cpu allocation
  drivers/perf: arm_pmu: manage interrupts per-cpu
  drivers/perf: arm_pmu: split irq request from enable

 drivers/perf/arm_pmu.c       | 450 ++++++++++++++++++++-----------------------
 include/linux/perf/arm_pmu.h |   4 +-
 2 files changed, 210 insertions(+), 244 deletions(-)

-- 
1.9.1

             reply	other threads:[~2017-01-30 15:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 15:31 Mark Rutland [this message]
2017-01-30 15:31 ` [PATCH 1/3] drivers/perf: arm_pmu: rework per-cpu allocation Mark Rutland
2017-01-30 15:31 ` [PATCH 2/3] drivers/perf: arm_pmu: manage interrupts per-cpu Mark Rutland
2017-01-30 15:31 ` [PATCH 3/3] drivers/perf: arm_pmu: split irq request from enable Mark Rutland
  -- strict thread matches above, loose matches on Subject: below --
2017-02-10 11:05 [PATCH 0/3] drivers/perf: arm_pmu: rework IRQ management Mark Rutland

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=1485790279-3139-1-git-send-email-mark.rutland@arm.com \
    --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).