All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: will@kernel.org
Cc: mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org,
	linux-perf-users@vger.kernel.org, allen.wang@hj-micro.com,
	peter.du@hj-micro.com, andy.xu@hj-micro.com
Subject: [PATCH 0/3] perf/arm-ni: IRQ improvements
Date: Tue, 13 May 2025 16:38:57 +0100	[thread overview]
Message-ID: <cover.1747149165.git.robin.murphy@arm.com> (raw)

Hi all,

While the previous attempt[1] was missing some important aspects, it's
a valid problem to solve, so I figured I'd take a look myself. This
ended up turning into a slightly wider cleanup, but I think the end
result is nice enough.

As usual I don't have anything to test this on, so if there are any
silly mistakes left that the compiler couldn't catch please do let me
know.

Thanks,
Robin.

[1] https://lore.kernel.org/all/20250410114214.1599777-3-allen.wang@hj-micro.com/


Robin Murphy (2):
  perf/arm-ni: Set initial IRQ affinity
  perf/arm-ni: Consolidate CPU affinity handling

Shouping Wang (1):
  perf/arm-ni: Support sharing IRQs within an NI instance

 drivers/perf/arm-ni.c | 148 ++++++++++++++++++++++++------------------
 1 file changed, 84 insertions(+), 64 deletions(-)

-- 
2.39.2.101.g768bb238c484.dirty



             reply	other threads:[~2025-05-13 15:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 15:38 Robin Murphy [this message]
2025-05-13 15:38 ` [PATCH 1/3] perf/arm-ni: Set initial IRQ affinity Robin Murphy
2025-05-13 15:38 ` [PATCH 2/3] perf/arm-ni: Consolidate CPU affinity handling Robin Murphy
2025-05-13 15:39 ` [PATCH 3/3] perf/arm-ni: Support sharing IRQs within an NI instance Robin Murphy
2025-05-19 12:29   ` Will Deacon
2025-05-19 14:57     ` Robin Murphy
2025-07-04 17:47       ` Will Deacon
2025-05-16 11:46 ` [PATCH 0/3] perf/arm-ni: IRQ improvements Shouping Wang
2025-07-04 17:44 ` Will Deacon

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=cover.1747149165.git.robin.murphy@arm.com \
    --to=robin.murphy@arm.com \
    --cc=allen.wang@hj-micro.com \
    --cc=andy.xu@hj-micro.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=peter.du@hj-micro.com \
    --cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.