public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Sascha Bischoff <sascha.bischoff@arm.com>,
	Timothy Hayes <timothy.hayes@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] irqchip/gic-v5: Remove IRQD_RESEND_WHEN_IN_PROGRESS for ITS IRQs
Date: Fri, 1 Aug 2025 16:01:09 +0200	[thread overview]
Message-ID: <aIzIpbQOcxmWOwvs@lpieralisi> (raw)
In-Reply-To: <86seib6x7b.wl-maz@kernel.org>

On Fri, Aug 01, 2025 at 01:30:32PM +0100, Marc Zyngier wrote:
> On Fri, 01 Aug 2025 08:58:20 +0100,
> Lorenzo Pieralisi <lpieralisi@kernel.org> wrote:
> > 
> > GICv5 LPI interrupts have an active state hence they cannot retrigger
> > while the IRQ is being handled.
> > 
> > Therefore setting IRQD_RESEND_WHEN_IN_PROGRESS for GICv5 ITS
> > interrupts provides no benefit and it is useless (and confusing),
> > it solves an issue that cannot happen.
> 
> This doesn't read very well. How about:
> 
> "Therefore, setting the IRQD_RESEND_WHEN_IN_PROGRESS flag on LPIs
>  is pointless, as the situation this flag caters for cannot happen".

Yes it is clearer, I can respin a v2 unless Thomas can update the log
please while applying it ? Just let me know.

Thanks,
Lorenzo

> > Remove it.
> > 
> > Signed-off-by: Lorenzo Pieralisi <lpieralisi@kernel.org>
> > Cc: Thomas Gleixner <tglx@linutronix.de>
> > Cc: Marc Zyngier <maz@kernel.org>
> > ---
> >  drivers/irqchip/irq-gic-v5-its.c | 1 -
> >  1 file changed, 1 deletion(-)
> > 
> > diff --git a/drivers/irqchip/irq-gic-v5-its.c b/drivers/irqchip/irq-gic-v5-its.c
> > index 340640fdbdf6..9290ac741949 100644
> > --- a/drivers/irqchip/irq-gic-v5-its.c
> > +++ b/drivers/irqchip/irq-gic-v5-its.c
> > @@ -973,7 +973,6 @@ static int gicv5_its_irq_domain_alloc(struct irq_domain *domain, unsigned int vi
> >  		irqd = irq_get_irq_data(virq + i);
> >  		irqd_set_single_target(irqd);
> >  		irqd_set_affinity_on_activate(irqd);
> > -		irqd_set_resend_when_in_progress(irqd);
> >  	}
> >  
> >  	return 0;
> > 
> 
> With that,
> 
> Reviewed-by: Marc Zyngier <maz@kernel.org>
> 
> 	M.
> 
> -- 
> Without deviation from the norm, progress is not possible.


  reply	other threads:[~2025-08-01 14:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-01  7:58 [PATCH 0/3] irqchip/gic-v5: Minor clean-ups/fixes Lorenzo Pieralisi
2025-08-01  7:58 ` [PATCH 1/3] irqchip/gic-v5: iwb: Fix iounmap probe failure path Lorenzo Pieralisi
2025-08-01 12:26   ` Marc Zyngier
2025-08-01  7:58 ` [PATCH 2/3] irqchip/gic-v5: iwb: Remove module boilerplate Lorenzo Pieralisi
2025-08-01 12:24   ` Marc Zyngier
2025-08-01 14:04     ` Lorenzo Pieralisi
2025-08-01  7:58 ` [PATCH 3/3] irqchip/gic-v5: Remove IRQD_RESEND_WHEN_IN_PROGRESS for ITS IRQs Lorenzo Pieralisi
2025-08-01 12:30   ` Marc Zyngier
2025-08-01 14:01     ` Lorenzo Pieralisi [this message]
2025-08-05  9:30 ` [PATCH 0/3] irqchip/gic-v5: Minor clean-ups/fixes Lorenzo Pieralisi

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=aIzIpbQOcxmWOwvs@lpieralisi \
    --to=lpieralisi@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=sascha.bischoff@arm.com \
    --cc=tglx@linutronix.de \
    --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