From: Marc Zyngier <maz@kernel.org>
To: Luigi Rizzo <lrizzo@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Luigi Rizzo <rizzo.unipi@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Sean Christopherson <seanjc@google.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH 1/6] genirq: platform wide interrupt moderation: Documentation, Kconfig, irq_desc
Date: Thu, 13 Nov 2025 19:02:12 +0000 [thread overview]
Message-ID: <86h5uxu56z.wl-maz@kernel.org> (raw)
In-Reply-To: <CAMOZA0+nKMvN_u7Di=2ODcMYgfyLXfHtvN1uDy3YdMR-kh5c1A@mail.gmail.com>
On Thu, 13 Nov 2025 14:55:55 +0000,
Luigi Rizzo <lrizzo@google.com> wrote:
>
> On Thu, Nov 13, 2025 at 3:42 PM Marc Zyngier <maz@kernel.org> wrote:
> > [...]
>
> >
> > The descriptions are also massively x86-specific. That's probably OK
> > for the stuff you care about, but I'd certainly would want things to
> > be a bit more abstract and applicable to all architectures.
>
> Absolutely.
>
> > I also note that since you explicitly check for handle_edge_irq() in
> > set_moderation_mode(), this will not work on anything GIC related, or
> > any other architecture that uses the fasteoi flows. I really wonder
> > why you are not looking at the actual trigger mode instead...
>
> sure, that would be the best thing. Any suggestions on how to fix the
> check ?
I made that suggestion already: check the trigger mode (the interrupt
"type") and only apply this to edge interrupts (and stop mentioning
MSIs, for which some architectures have a level variant).
> > Until you fix it, please refrain from touching the GICv3 code, and
> > make sure this is solely enabled on x86 -- it clearly wasn't tested on
> > anything else.
>
> FWIW I did verify correct operation and performance boost on arm64,
> both network and nvme (this was a previous version which
> did not restrict to handle_edge_irq).
You do realise that what is not on the list doesn't exist, right? ;-)
> Also FWIW there should be nothing architecture-specific in this series.
We're in strong agreement here.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-11-13 19:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 19:24 [PATCH 0/6] platform wide software interrupt moderation Luigi Rizzo
2025-11-12 19:24 ` [PATCH 1/6] genirq: platform wide interrupt moderation: Documentation, Kconfig, irq_desc Luigi Rizzo
2025-11-13 8:17 ` Thomas Gleixner
2025-11-13 9:44 ` Thomas Gleixner
2025-11-13 13:25 ` Marc Zyngier
2025-11-13 13:33 ` Luigi Rizzo
2025-11-13 14:42 ` Marc Zyngier
2025-11-13 14:55 ` Luigi Rizzo
2025-11-13 19:02 ` Marc Zyngier [this message]
2025-11-12 19:24 ` [PATCH 2/6] genirq: soft_moderation: add base files, procfs hooks Luigi Rizzo
2025-11-13 9:29 ` Thomas Gleixner
2025-11-13 10:24 ` Thomas Gleixner
2025-11-13 22:42 ` Luigi Rizzo
2025-11-13 22:32 ` Luigi Rizzo
2025-11-13 9:40 ` Thomas Gleixner
2025-11-12 19:24 ` [PATCH 3/6] genirq: soft_moderation: activate hooks in handle_irq_event() Luigi Rizzo
2025-11-13 9:45 ` Thomas Gleixner
2025-11-14 8:27 ` Luigi Rizzo
2025-11-12 19:24 ` [PATCH 4/6] genirq: soft_moderation: implement adaptive moderation Luigi Rizzo
2025-11-13 10:15 ` Thomas Gleixner
2025-11-12 19:24 ` [PATCH 5/6] x86/irq: soft_moderation: add support for posted_msi (intel) Luigi Rizzo
2025-11-12 19:24 ` [PATCH 6/6] genirq: soft_moderation: implement per-driver defaults (nvme and vfio) Luigi Rizzo
2025-11-13 10:18 ` Thomas Gleixner
2025-11-13 10:42 ` Luigi Rizzo
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=86h5uxu56z.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrizzo@google.com \
--cc=pabeni@redhat.com \
--cc=rizzo.unipi@gmail.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.