From: Ashok Raj <ashok.raj@oss.qualcomm.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Vladimir Murzin <vladimir.murzin@arm.com>,
Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Jinjie Ruan <ruanjinjie@huawei.com>,
Liaochang <liaochang1@huawei.com>, Radu Rendec <radu@rendec.net>,
Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>,
Sathvika Vasireddy <sathvika.vasireddy@oss.qualcomm.com>,
Ashok Raj <ashoraj@qti.qualcomm.com>,
Ashok Raj <ashok.raj@oss.qualcomm.com>
Subject: Re: [RFC PATCH v1 0/2] genirq: add migratable NMI registration and show NMI counts
Date: Tue, 17 Nov 2026 14:39:30 -0800 [thread overview]
Message-ID: <avzXou6jLGuZYTDp@hu-ashoraj-lv.qualcomm.com> (raw)
In-Reply-To: <87h5hf8b5v.wl-maz@kernel.org>
On Tue, Nov 17, 2026 at 08:18:04PM +0000, Marc Zyngier wrote:
> >
> > I think what i quoted is true for regular interrupts, but NMI's there is no
> > IRQD_IRQ_INPROGRESS serialization. So that overlap as you quote might
> > be possible.
> >
> > I'll need more time to stare at the code and rebase my RFC and post a
> > coherent series that uses it to get the full picture.
>
> When you do that, please don't mix functionalities and tests as you
> did in the first patch. Slap the tests at the end of the series
> instead, as separate patches.
>
Thanks for the tip. Certainly!
--
/ashok.raj
ashok.raj@oss.qualcomm.com
Qualcomm Inc
prev parent reply other threads:[~2026-11-17 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 23:49 Ashok Raj
2026-11-14 23:49 ` [RFC PATCH v1 1/2] genirq: Add migratable NMI registration mode Ashok Raj
2026-11-14 23:49 ` [RFC PATCH v1 2/2] genirq/proc: Show NMI interrupt counts in /proc/interrupts Ashok Raj
2026-11-16 10:38 ` [RFC PATCH v1 0/2] genirq: add migratable NMI registration and show NMI counts Vladimir Murzin
2026-11-16 18:31 ` Ashok Raj
2026-11-17 18:40 ` Ashok Raj
2026-11-17 20:18 ` Marc Zyngier
2026-11-17 22:39 ` Ashok Raj [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=avzXou6jLGuZYTDp@hu-ashoraj-lv.qualcomm.com \
--to=ashok.raj@oss.qualcomm.com \
--cc=ashoraj@qti.qualcomm.com \
--cc=catalin.marinas@arm.com \
--cc=jonathan.cameron@oss.qualcomm.com \
--cc=liaochang1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=radu@rendec.net \
--cc=ruanjinjie@huawei.com \
--cc=sathvika.vasireddy@oss.qualcomm.com \
--cc=vladimir.murzin@arm.com \
--cc=will@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®