public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Nilay Shroff <nilay@linux.ibm.com>
To: linux-nvme@lists.infradead.org
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
	hare@suse.de, dwagner@suse.de, wenxiong@linux.ibm.com,
	gjoyce@ibm.com, Nilay Shroff <nilay@linux.ibm.com>
Subject: [PATCHv3 6/7] nvme: export controller reset event count via sysfs
Date: Fri, 20 Feb 2026 23:18:51 +0530	[thread overview]
Message-ID: <20260220175024.292898-7-nilay@linux.ibm.com> (raw)
In-Reply-To: <20260220175024.292898-1-nilay@linux.ibm.com>

The NVMe controller transitions into the RESETTING state during error
recovery, link instability, firmware activation, or when a reset is
explicitly triggered by the user.

Expose a controller reset event count via sysfs attribute named
"reset_events" to provide visibility into these RESETTING state
transitions. Observing the frequency of reset events can help users
identify issues such as PCIe errors or unstable fabric links. This
counter is also writable thus allowing user to reset its value, if
needed.

This counter can also be consumed by monitoring tools such as nvme-top
to improve controller-level observability.

Signed-off-by: Nilay Shroff <nilay@linux.ibm.com>
---
 drivers/nvme/host/core.c  |  2 ++
 drivers/nvme/host/nvme.h  |  1 +
 drivers/nvme/host/sysfs.c | 27 +++++++++++++++++++++++++++
 3 files changed, 30 insertions(+)

diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index d07e2ed9e494..1cba460d8563 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -593,6 +593,8 @@ bool nvme_change_ctrl_state(struct nvme_ctrl *ctrl,
 		case NVME_CTRL_NEW:
 		case NVME_CTRL_LIVE:
 			changed = true;
+			WRITE_ONCE(ctrl->nr_reset,
+				size_add(READ_ONCE(ctrl->nr_reset), 1));
 			fallthrough;
 		default:
 			break;
diff --git a/drivers/nvme/host/nvme.h b/drivers/nvme/host/nvme.h
index b1ce2857899a..5d90e5fa7298 100644
--- a/drivers/nvme/host/nvme.h
+++ b/drivers/nvme/host/nvme.h
@@ -360,6 +360,7 @@ struct nvme_ctrl {
 	struct work_struct fw_act_work;
 	unsigned long events;
 	size_t errors;
+	size_t nr_reset;
 #ifdef CONFIG_NVME_MULTIPATH
 	/* asymmetric namespace access: */
 	u8 anacap;
diff --git a/drivers/nvme/host/sysfs.c b/drivers/nvme/host/sysfs.c
index 790bf875dd1b..f3e6c7208315 100644
--- a/drivers/nvme/host/sysfs.c
+++ b/drivers/nvme/host/sysfs.c
@@ -710,6 +710,32 @@ struct device_attribute dev_attr_adm_errors =
 	__ATTR(command_error_count, 0644,
 			nvme_adm_errors_show, nvme_adm_errors_store);
 
+static ssize_t reset_events_show(struct device *dev,
+		   struct device_attribute *attr, char *buf)
+{
+	struct nvme_ctrl *ctrl = dev_get_drvdata(dev);
+
+	return sysfs_emit(buf, "%lu\n", READ_ONCE(ctrl->nr_reset));
+}
+
+static ssize_t reset_events_store(struct device *dev,
+		struct device_attribute *attr, const char *buf, size_t count)
+{
+	int err;
+	unsigned long reset_cnt;
+	struct nvme_ctrl *ctrl = dev_get_drvdata(dev);
+
+	err = kstrtoul(buf, 0, &reset_cnt);
+	if (err)
+		return -EINVAL;
+
+	WRITE_ONCE(ctrl->nr_reset, reset_cnt);
+
+	return count;
+}
+
+static DEVICE_ATTR_RW(reset_events);
+
 #ifdef CONFIG_NVME_HOST_AUTH
 static ssize_t nvme_ctrl_dhchap_secret_show(struct device *dev,
 		struct device_attribute *attr, char *buf)
@@ -857,6 +883,7 @@ static struct attribute *nvme_dev_attrs[] = {
 #endif
 	&dev_attr_adm_passthru_err_log_enabled.attr,
 	&dev_attr_adm_errors.attr,
+	&dev_attr_reset_events.attr,
 	NULL
 };
 
-- 
2.52.0



  parent reply	other threads:[~2026-02-20 17:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-20 17:48 [PATCHv3 0/7] nvme: export additional diagnostic counters via sysfs Nilay Shroff
2026-02-20 17:48 ` [PATCHv3 1/7] nvme: export command retry count " Nilay Shroff
2026-02-20 17:48 ` [PATCHv3 2/7] nvme: export multipath failover " Nilay Shroff
2026-02-20 17:48 ` [PATCHv3 3/7] nvme: export command error counters " Nilay Shroff
2026-02-20 17:48 ` [PATCHv3 4/7] nvme: export I/O requeue count when no path is available " Nilay Shroff
2026-02-20 17:48 ` [PATCHv3 5/7] nvme: export I/O failure " Nilay Shroff
2026-02-20 17:48 ` Nilay Shroff [this message]
2026-02-20 17:48 ` [PATCHv3 7/7] nvme: export controller reconnect event count " Nilay Shroff
2026-02-22 12:36 ` [PATCHv3 0/7] nvme: export additional diagnostic counters " Venkat
2026-02-22 14:10   ` Nilay Shroff
2026-02-22 15:06     ` Venkat Rao Bagalkote
2026-02-26  5:37 ` Chaitanya Kulkarni
2026-03-04 14:33 ` Nilay Shroff
2026-03-06 16:02   ` Keith Busch
2026-03-08 18:55     ` Nilay Shroff
2026-03-09 15:32       ` John Garry
2026-03-19 15:55         ` Nilay Shroff
2026-03-16 12:56       ` Nilay Shroff

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=20260220175024.292898-7-nilay@linux.ibm.com \
    --to=nilay@linux.ibm.com \
    --cc=axboe@kernel.dk \
    --cc=dwagner@suse.de \
    --cc=gjoyce@ibm.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    --cc=wenxiong@linux.ibm.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