mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Troy Mitchell" <troy.mitchell@linux.dev>
To: "Thomas Gleixner" <tglx@kernel.org>
Cc: "Troy Mitchell" <troy.mitchell@linux.dev>,
	"Anup Patel" <anup@brainfault.org>,
	"Radu Rendec" <radu@rendec.net>, "Paul Walmsley" <pjw@kernel.org>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Alexandre Ghiti" <alex@ghiti.fr>,
	"Anup Patel" <apatel@ventanamicro.com>,
	<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] irqchip/riscv-aplic: Process pending affinity changes on EOI
Date: Tue, 10 Nov 2026 07:15:00 +0000	[thread overview]
Message-ID: <DMRCGHS3V729.FIU61TS3JYWD@linux.dev> (raw)
In-Reply-To: <87pkweuxbe.ffs@fw13>

[-- Attachment #1: Type: text/plain, Size: 893 bytes --]

On Mon, 09 Nov 2026 11:13:41 +0100, Thomas Gleixner wrote:
> On Wed, Nov 04 2026 at 14:21, Troy Mitchell wrote:
> > IMSIC rejects an affinity change with -EBUSY while a previous vector
> > move is still in flight, and the IRQ core then records the new mask
> > as pending. The change is meant to be applied by irq_move_irq() in
> > the IMSIC irq_ack callback, but APLIC MSI interrupts are handled by
> > handle_fasteoi_irq(), which does not call irq_ack.
>
> Which is a bug when the interrupt is edge type.
>
> Edge type interrupts are fire and forget from the device point of
> view. So you want handle_edge_irq() for them, which issues the ack()
> _before_ the handler is invoked. Otherwise you can lose interrupts.
Right, I can reproduce the lost edge here. v2 will use handle_edge_irq()
for edge sources and handle_fasteoi_ack_irq() for level sources.

-- 
Troy Mitchell

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

      reply	other threads:[~2026-11-10  7:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 14:21 Troy Mitchell
2026-11-09 10:13 ` Thomas Gleixner
2026-11-10  7:15   ` Troy Mitchell [this message]

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=DMRCGHS3V729.FIU61TS3JYWD@linux.dev \
    --to=troy.mitchell@linux.dev \
    --cc=alex@ghiti.fr \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=apatel@ventanamicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=radu@rendec.net \
    --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

all inboxes | Powered by JetHome®