From: Sascha Bischoff <sascha.bischoff@arm.com>
To: Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: Marc Zyngier <maz@kernel.org>, Thomas Gleixner <tglx@kernel.org>,
Radu Rendec <radu@rendec.net>,
Timothy Hayes <timothy.hayes@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Jonathan Cameron <jic23@kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Sashiko AI <sashiko-bot@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 04/10] irqchip/gic-v5: Serialise ITS invalidation commands
Date: Wed, 18 Nov 2026 15:39:47 +0000 [thread overview]
Message-ID: <535a378e-4d68-4a5c-a85d-3366e2a1626c@arm.com> (raw)
In-Reply-To: <auw-5EyY_aifcv1N@red-moon>
On 05/11/2026 08:31, Lorenzo Pieralisi wrote:
> On Wed, Nov 04, 2026 at 05:47:58PM +0000, Sascha Bischoff wrote:
>> The ITS uses the shared DIDR and EIDR registers to select the DeviceID
>> and EventID whose translation is to be invalidated. Event
>> invalidations for different IRQs can overlap, as can an event
>> invalidation and a device invalidation. The per-IRQ descriptor lock
>> does not serialise these commands, so writes can interleave and cause
>> an invalidation to use the DeviceID or EventID of another IRQ being
>> invalidated concurrently on a different CPU.
>>
>> Serialise the command register writes and STATUSR.IDLE polls for both
>> invalidation paths with a per-ITS raw spinlock. The KVM
>> gicv5_its_set_vcpu_affinity() callback calls the event invalidation
>> helper via irq_set_vcpu_affinity(), which holds the IRQ descriptor
>> lock. This path cannot sleep, so use atomic polling.
>
> Same comment here as IRS sync. This one though looks like a host
> driver bug that can happen regardless of KVM, so I'd just fix it
> and remove/rephrase this paragraph.
Done, thanks!
>
>> Fixes: 57d72196dfc8 ("irqchip/gic-v5: Add GICv5 ITS support")
>> Reported-by: Sashiko AI <sashiko-bot@kernel.org>
>> Link: https://sashiko.dev/#/patchset/20261016155741.979985-1-sascha.bischoff@arm.com?part=11
>
> Again, this is linking to a report on a series that wasn't merged
> yet but probably it makes sense to leave it there for context.
Yeah, I was just trying to make it clear where this was reported and how.
Thanks,
Sascha
>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Sascha Bischoff <sascha.bischoff@arm.com>
>> ---
>> drivers/irqchip/irq-gic-v5-its.c | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>
> Acked-by: Lorenzo Pieralisi <lpieralisi@kernel.org>
>
>> diff --git a/drivers/irqchip/irq-gic-v5-its.c b/drivers/irqchip/irq-gic-v5-its.c
>> index 28e39b065de0e..6d98f3dbe34b6 100644
>> --- a/drivers/irqchip/irq-gic-v5-its.c
>> +++ b/drivers/irqchip/irq-gic-v5-its.c
>> @@ -16,6 +16,7 @@
>> #include <linux/of_address.h>
>> #include <linux/of_irq.h>
>> #include <linux/slab.h>
>> +#include <linux/spinlock.h>
>>
>> #include <linux/irqchip.h>
>> #include <linux/irqchip/arm-gic-v5.h>
>> @@ -28,6 +29,8 @@
>> struct gicv5_its_chip_data {
>> struct xarray its_devices;
>> struct mutex dev_alloc_lock;
>> + /* Event and device invalidation commands share DIDR. */
>> + raw_spinlock_t inv_lock;
>> struct fwnode_handle *fwnode;
>> struct gicv5_its_devtab_cfg devtab_cfgr;
>> void __iomem *its_base;
>> @@ -129,6 +132,8 @@ static int gicv5_its_itt_cache_inv(struct gicv5_its_chip_data *its, u32 device_i
>> eidr = FIELD_PREP(GICV5_ITS_EIDR_EVENTID, event_id);
>> eventr = FIELD_PREP(GICV5_ITS_INV_EVENTR_I, 0x1);
>>
>> + guard(raw_spinlock_irqsave)(&its->inv_lock);
>> +
>> its_writeq_relaxed(its, didr, GICV5_ITS_DIDR);
>> its_writel_relaxed(its, eidr, GICV5_ITS_EIDR);
>> its_writel_relaxed(its, eventr, GICV5_ITS_INV_EVENTR);
>> @@ -371,6 +376,9 @@ static int gicv5_its_device_cache_inv(struct gicv5_its_chip_data *its,
>> FIELD_PREP(GICV5_ITS_INV_DEVICER_EVENTID_BITS,
>> its_dev->itt_cfg.event_id_bits) |
>> FIELD_PREP(GICV5_ITS_INV_DEVICER_L1, 0x0);
>> +
>> + guard(raw_spinlock_irqsave)(&its->inv_lock);
>> +
>> its_writeq_relaxed(its, didr, GICV5_ITS_DIDR);
>> its_writel_relaxed(its, devicer, GICV5_ITS_INV_DEVICER);
>>
>> @@ -1112,6 +1120,7 @@ static int __init gicv5_its_init_bases(void __iomem *its_base, struct fwnode_han
>> return -ENOMEM;
>>
>> mutex_init(&its_node->dev_alloc_lock);
>> + raw_spin_lock_init(&its_node->inv_lock);
>> xa_init(&its_node->its_devices);
>> its_node->fwnode = handle;
>> its_node->its_base = its_base;
>>
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2026-11-18 15:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 17:47 [PATCH v2 00/10] irqchip/gic-v5: Fix misc IRS and ITS host driver issues Sascha Bischoff
2026-11-04 17:47 ` [PATCH v2 01/10] irqchip/gic-v5: Reject SPIs not backed by an IRS Sascha Bischoff
2026-11-05 7:35 ` Lorenzo Pieralisi
2026-11-18 15:32 ` Sascha Bischoff
2026-11-04 17:47 ` [PATCH v2 02/10] irqchip/gic-v5: Only set IRS DPS when 1ofN routing is supported Sascha Bischoff
2026-11-04 17:47 ` [PATCH v2 03/10] irqchip/gic-v5: Serialise IRS synchronisation requests Sascha Bischoff
2026-11-05 7:48 ` Lorenzo Pieralisi
2026-11-18 15:34 ` Sascha Bischoff
2026-11-04 17:47 ` [PATCH v2 04/10] irqchip/gic-v5: Serialise ITS invalidation commands Sascha Bischoff
2026-11-05 8:31 ` Lorenzo Pieralisi
2026-11-18 15:39 ` Sascha Bischoff [this message]
2026-11-04 17:47 ` [PATCH v2 05/10] irqchip/gic-v5: Use linear DT and ITT when L2 covers all IDs Sascha Bischoff
2026-11-04 17:48 ` [PATCH v2 06/10] irqchip/gic-v5: Honour ACPI ITS noncoherent flag Sascha Bischoff
2026-11-04 17:48 ` [PATCH v2 07/10] irqchip/gic-v5: Use firmware node name in ITS warning Sascha Bischoff
2026-11-04 17:48 ` [PATCH v2 08/10] irqchip/gic-v5: Invalidate ITS device cache before freeing ITT Sascha Bischoff
2026-11-04 17:48 ` [PATCH v2 09/10] irqchip/gic-v5: Clean the allocated linear device table size Sascha Bischoff
2026-11-05 7:37 ` Lorenzo Pieralisi
2026-11-04 17:48 ` [PATCH v2 10/10] irqchip/gic-v5: Release ITS MMIO region on DT probe failure Sascha Bischoff
2026-11-12 14:58 ` [PATCH v2 00/10] irqchip/gic-v5: Fix misc IRS and ITS host driver issues Fuad Tabba
2026-11-16 12:14 ` Lorenzo Pieralisi
2026-11-16 13:28 ` Fuad Tabba
2026-11-16 14:06 ` Lorenzo Pieralisi
2026-11-18 14:58 ` Sascha Bischoff
2026-11-18 15:16 ` Fuad Tabba
2026-11-18 15:20 ` 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=535a378e-4d68-4a5c-a85d-3366e2a1626c@arm.com \
--to=sascha.bischoff@arm.com \
--cc=catalin.marinas@arm.com \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=maz@kernel.org \
--cc=radu@rendec.net \
--cc=rafael.j.wysocki@intel.com \
--cc=sashiko-bot@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=timothy.hayes@arm.com \
/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