From: "Gowans, James" <jgowans@amazon.com>
To: "maz@kernel.org" <maz@kernel.org>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"Raslan, KarimAllah" <karahmed@amazon.com>,
"liaochang1@huawei.com" <liaochang1@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"zouyipeng@huawei.com" <zouyipeng@huawei.com>,
"chris.zjh@huawei.com" <chris.zjh@huawei.com>
Subject: Re: [PATCH v3 2/2] genirq: fasteoi supports resend on concurrent invoke
Date: Wed, 7 Jun 2023 12:21:10 +0000 [thread overview]
Message-ID: <9c831b0b0b0f067f48841903b5173e3c97f84292.camel@amazon.com> (raw)
In-Reply-To: <87jzwgo715.wl-maz@kernel.org>
On Tue, 2023-06-06 at 18:05 +0100, Marc Zyngier wrote:
>
> On Mon, 05 Jun 2023 16:57:23 +0100,
> James Gowans <jgowans@amazon.com> wrote:
> > ... and enable that functionality for GIC-v3 only.
>
> nit: drop the multi-line subject.
Would you prefer two commits - one to introduce the functionality and one
to enable it for GIC-v3?
> diff --git a/include/linux/irq.h b/include/linux/irq.h
> > index b1b28affb32a..b76cc90faebd 100644
> > --- a/include/linux/irq.h
> > +++ b/include/linux/irq.h
> > @@ -223,6 +223,8 @@ struct irq_data {
> > * irq_chip::irq_set_affinity() when deactivated.
> > * IRQD_IRQ_ENABLED_ON_SUSPEND - Interrupt is enabled on suspend by irq pm if
> > * irqchip have flag IRQCHIP_ENABLE_WAKEUP_ON_SUSPEND set.
> > + * RQD_RESEND_WHEN_IN_PROGRESS - Interrupt may fire when already in progress in which
> > + * case it must be resent at the next available opportunity.
> > */
> > enum {
> > IRQD_TRIGGER_MASK = 0xf,
> > @@ -249,6 +251,7 @@ enum {
> > IRQD_HANDLE_ENFORCE_IRQCTX = (1 << 28),
> > IRQD_AFFINITY_ON_ACTIVATE = (1 << 29),
> > IRQD_IRQ_ENABLED_ON_SUSPEND = (1 << 30),
> > + IRQD_RESEND_WHEN_IN_PROGRESS = (1 << 31),
>
> Make this unsigned, as it otherwise has the potential to sign-extend
> and lead to "fun to debug" issues.
Ack, doing this change:
@@ -251,7 +251,7 @@ enum {
IRQD_HANDLE_ENFORCE_IRQCTX = (1 << 28),
IRQD_AFFINITY_ON_ACTIVATE = (1 << 29),
IRQD_IRQ_ENABLED_ON_SUSPEND = (1 << 30),
- IRQD_RESEND_WHEN_IN_PROGRESS = (1 << 31),
+ IRQD_RESEND_WHEN_IN_PROGRESS = (1U << 31),
};
(looks a bit odd having only this one unsigned though...)
Also fixing above typo which Randy pointed out.
> +++ b/kernel/irq/chip.c
> > @@ -692,8 +692,16 @@ void handle_fasteoi_irq(struct irq_desc *desc)
> >
> > raw_spin_lock(&desc->lock);
> >
> > - if (!irq_may_run(desc))
> > + /*
> > + * When an affinity change races with IRQ delivery, the next interrupt
>
> The race is with the IRQ *handling*.
Reworded.
>
> If you respin this series shortly (*with* a cover letter, please),
> I'll queue it so that it can simmer in -next for a bit.
Will do - just keen to see if you prefer the commit to be split.
JG
next prev parent reply other threads:[~2023-06-07 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 15:57 [PATCH v3 1/2] genirq: Expand doc for PENDING and REPLAY flags James Gowans
2023-06-05 15:57 ` [PATCH v3 2/2] genirq: fasteoi supports resend on concurrent invoke James Gowans
2023-06-06 2:06 ` Randy Dunlap
2023-06-06 17:05 ` Marc Zyngier
2023-06-07 12:21 ` Gowans, James [this message]
2023-06-07 13:13 ` Marc Zyngier
2023-06-08 12:12 ` Gowans, James
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=9c831b0b0b0f067f48841903b5173e3c97f84292.camel@amazon.com \
--to=jgowans@amazon.com \
--cc=chris.zjh@huawei.com \
--cc=karahmed@amazon.com \
--cc=liaochang1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
--cc=zouyipeng@huawei.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
all inboxes | Powered by JetHome®