From: Ciju Rajan K <crajank@nvidia.com>
To: <hdegoede@redhat.com>, <ilpo.jarvinen@linux.intel.com>,
<tglx@linutronix.de>, <andriy.shevchenko@linux.intel.com>,
<linux-kernel@vger.kernel.org>
Cc: <christophe.jaillet@wanadoo.fr>,
<platform-driver-x86@vger.kernel.org>, <vadimp@nvidia.com>,
Ciju Rajan K <crajank@nvidia.com>
Subject: [PATCH platform-next v2 0/2] Support for handling interrupt storm
Date: Tue, 23 Sep 2025 13:44:50 +0300 [thread overview]
Message-ID: <20250923104452.2407460-1-crajank@nvidia.com> (raw)
This patcheset contain:
Patch #1 Add fields for interrupt storm handling
Patch #2 Add support for handling interrupt storm
v0->v2
Comments pointed out by Ilpo:
- Renamed the macro MLXREG_HOTPLUG_WM_WINDOW to MLXREG_HOTPLUG_WM_WINDOW_MS to indicate milli seconds
- Removed the timestamp stored in wmark_high_ts and used jiffies directly
- Calculating the time window and storing it in the new variable wmark_window.
- Removed the variables wmark_low_ts and wmark_high_ts
- Used continue statement inside the time window check
Changes added by Ciju:
- Renamed variable wmark_low_cntr to wmark_cntr
- Fixed the time window to check for interrupt storm
Ciju Rajan K (2):
platform_data/mlxreg: Add fields for interrupt storm handling
platform/mellanox: mlxreg-hotplug: Add support for handling interrupt
storm
drivers/platform/mellanox/mlxreg-hotplug.c | 32 ++++++++++++++++++++--
include/linux/platform_data/mlxreg.h | 6 ++++
2 files changed, 36 insertions(+), 2 deletions(-)
--
2.47.2
next reply other threads:[~2025-09-23 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 10:44 Ciju Rajan K [this message]
2025-09-23 10:44 ` [PATCH platform-next v2 1/2] [PATCH platform-next 1/2] platform_data/mlxreg: Add fields for interrupt storm handling Ciju Rajan K
2025-09-23 10:58 ` Ilpo Järvinen
2025-09-23 12:10 ` Ciju Rajan K
2025-09-23 10:44 ` [PATCH platform-next v2 2/2] [PATCH platform-next 2/2] platform/mellanox: mlxreg-hotplug: Add support for handling interrupt storm Ciju Rajan K
2025-09-23 10:54 ` Ilpo Järvinen
2025-09-23 12:09 ` Ciju Rajan K
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=20250923104452.2407460-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