public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Sascha Bischoff <Sascha.Bischoff@arm.com>
To: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: nd <nd@arm.com>, Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Marc Zyngier <maz@kernel.org>, Thomas Gleixner <tglx@kernel.org>
Subject: [PATCH v2 0/3] irqchip/gic-v5: Tidy up LPI allocation
Date: Wed, 6 May 2026 09:36:42 +0000	[thread overview]
Message-ID: <20260506093634.382062-1-sascha.bischoff@arm.com> (raw)

LPIs are owned by the LPI domain, but the ITS MSI and IPI domains
currently allocate and free them directly. This exposes the parent's
allocation policy to child domains and requires the children to release
resources that belong to the parent.

Move LPI allocation and teardown into the LPI domain and remove the
exported wrappers that allowed external callers to manage LPIs
directly. Then update the LPI, IPI and ITS MSI domains to use range
allocation and teardown instead of enforcing one-by-one operation.

Thanks,
Sascha

---
Changes since v1:
* Re-wrote commit messages for patches 1 & 2 to be in keeping with the
  expected style.
* Cleaned up loops in patch 2 to use unsigned int and minimise usage
  of `virq + i` (using `virq++` instead). Thanks, Thomas.
* Added Reviewed-by tags.
* Added a Fixes tag to patch 2 as it does fix an existing bug.

v1: https://lore.kernel.org/all/20260430153352.3654325-1-sascha.bischoff@arm.com/

Sascha Bischoff (3):
  irqchip/gic-v5: Move LPI allocation into the LPI domain
  irqchip/gic-v5: Support range allocation for LPIs
  irqchip/gic-v5: Allocate ITS parent LPIs as a range

 drivers/irqchip/irq-gic-v5-its.c   | 34 +++--------
 drivers/irqchip/irq-gic-v5.c       | 98 ++++++++++++++++--------------
 include/linux/irqchip/arm-gic-v5.h |  3 -
 3 files changed, 60 insertions(+), 75 deletions(-)

-- 
2.34.1


             reply	other threads:[~2026-05-06  9:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06  9:36 Sascha Bischoff [this message]
2026-05-06  9:37 ` [PATCH v2 1/3] irqchip/gic-v5: Move LPI allocation into the LPI domain Sascha Bischoff
2026-05-06  9:37 ` [PATCH v2 2/3] irqchip/gic-v5: Support range allocation for LPIs Sascha Bischoff
2026-05-06  9:37 ` [PATCH v2 3/3] irqchip/gic-v5: Allocate ITS parent LPIs as a range Sascha Bischoff

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=20260506093634.382062-1-sascha.bischoff@arm.com \
    --to=sascha.bischoff@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=maz@kernel.org \
    --cc=nd@arm.com \
    --cc=tglx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox