From: Ciju Rajan K <crajank@nvidia.com>
To: <hdegoede@redhat.com>, <ilpo.jarvinen@linux.intel.com>,
<tglx@linutronix.de>
Cc: <christophe.jaillet@wanadoo.fr>,
<andriy.shevchenko@linux.intel.com>, <vadimp@nvidia.com>,
<platform-driver-x86@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Ciju Rajan K <crajank@nvidia.com>
Subject: [PATCH platform-next v4 0/2] Interrupt storm detection
Date: Thu, 15 Jan 2026 09:49:07 +0200 [thread overview]
Message-ID: <20260115074909.245852-1-crajank@nvidia.com> (raw)
This patcheset contain:
Patch #1 Add generic interrupt storm detection mechanism
Patch #2 Enabling interrupt storm detection for mlxreg-hotplug driver
v0->v4
- Impletemented generic interrupt storm detection as suggested
by Thomas Gleixner.
- Updated the mlxreg-hotplug driver to make use of generic interrupt
storm detection.
- Modified the logic in mlxreg-hotplug driver to track per device
interrupts for the the shared IRQ based on the call back function
provided by generic interrupt storm detection.
- Addressed the comments pointed out by Ilpo on earlier versions.
Ciju Rajan K (2):
kernel/irq: Add generic interrupt storm detection mechanism
platform/mellanox: mlxreg-hotplug: Enabling interrupt storm detection
drivers/platform/mellanox/mlxreg-hotplug.c | 74 +++++++++++++++++-
include/linux/interrupt.h | 13 ++++
include/linux/irqdesc.h | 20 +++++
include/linux/platform_data/mlxreg.h | 4 +
kernel/irq/manage.c | 4 +
kernel/irq/spurious.c | 87 ++++++++++++++++++++++
6 files changed, 200 insertions(+), 2 deletions(-)
--
2.47.3
next reply other threads:[~2026-01-15 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 7:49 Ciju Rajan K [this message]
2026-01-15 7:49 ` [PATCH platform-next v4 1/2] kernel/irq: Add generic interrupt storm detection mechanism Ciju Rajan K
2026-01-15 8:29 ` Andy Shevchenko
2026-01-15 14:00 ` kernel test robot
2026-01-15 14:11 ` kernel test robot
2026-01-15 7:49 ` [PATCH platform-next v4 2/2] platform/mellanox: mlxreg-hotplug: Enabling interrupt storm detection Ciju Rajan K
2026-01-15 8:34 ` Andy Shevchenko
2026-01-15 14:43 ` kernel test robot
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=20260115074909.245852-1-crajank@nvidia.com \
--to=crajank@nvidia.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vadimp@nvidia.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