public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Thomas Gleixner <tglx@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Robin Murphy <robin.murphy@arm.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] irqchip/gic-v3-its: Limit number of per-device MSIs to the range the ITS supports
Date: Sat, 07 Feb 2026 22:25:29 +0000	[thread overview]
Message-ID: <86zf5kb38m.wl-maz@kernel.org> (raw)
In-Reply-To: <87h5rsb64v.ffs@tglx>

On Sat, 07 Feb 2026 21:22:56 +0000,
Thomas Gleixner <tglx@kernel.org> wrote:
> 
> On Fri, Feb 06 2026 at 15:48, Marc Zyngier wrote:
> 
> > The ITS driver blindly assumes that EventIDs are in abundant supply,
> > to the point where it never checks how many the HW actually supports.
> >
> > It turns out that some pretty esoteric integrations make it so that
> > only a few bits are available, all the way down to a. single. bit.
> >
> > Enforce the advertised limitation at the point of allocating the
> > device structure, and hope that the endpoint driver can deal with
> > such limitation.
> >
> > Signed-off-by: Marc Zyngier <maz@kernel.org>
> > Cc: stable@vger.kernel.org
> 
> Can you please provide a Fixes tag?

That'd be

Fixes: 84a6a2e7fc18d ("irqchip: GICv3: ITS: device allocation and configuration")

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2026-02-07 22:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06 15:48 [PATCH] irqchip/gic-v3-its: Limit number of per-device MSIs to the range the ITS supports Marc Zyngier
2026-02-06 16:01 ` Robin Murphy
2026-02-07 21:22 ` Thomas Gleixner
2026-02-07 22:25   ` Marc Zyngier [this message]
2026-02-08 18:48 ` Zenghui Yu
2026-02-17 10:02 ` [tip: irq/urgent] " tip-bot2 for Marc Zyngier

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=86zf5kb38m.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=stable@vger.kernel.org \
    --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