From: Guixin Liu <kanie@linux.alibaba.com>
To: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Nilay Shroff <nilay@linux.ibm.com>,
Daniel Wagner <dwagner@suse.de>, Hannes Reinecke <hare@suse.de>
Cc: linux-nvme@lists.infradead.org
Subject: [PATCH 1/2] nvme: define the SMART / Health Status async event bit
Date: Mon, 9 Nov 2026 20:02:03 +0800 [thread overview]
Message-ID: <20261109120207.1352165-2-kanie@linux.alibaba.com> (raw)
In-Reply-To: <20261109120207.1352165-1-kanie@linux.alibaba.com>
NVMe 2.x requires controllers to support the SMART / Health Status
asynchronous event (OAES bit 1), but the only event bits the header
defines are namespace attribute, firmware activation, ANA change and
discovery change. Define the missing bit so the host can subscribe to
the event.
Signed-off-by: Guixin Liu <kanie@linux.alibaba.com>
---
include/linux/nvme.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/nvme.h b/include/linux/nvme.h
index 6248711784b37..2b4f8e269d12d 100644
--- a/include/linux/nvme.h
+++ b/include/linux/nvme.h
@@ -867,6 +867,7 @@ enum {
};
enum {
+ NVME_AEN_BIT_SMART = 1,
NVME_AEN_BIT_NS_ATTR = 8,
NVME_AEN_BIT_FW_ACT = 9,
NVME_AEN_BIT_ANA_CHANGE = 11,
@@ -874,6 +875,7 @@ enum {
};
enum {
+ NVME_AEN_CFG_SMART = 1 << NVME_AEN_BIT_SMART,
NVME_AEN_CFG_NS_ATTR = 1 << NVME_AEN_BIT_NS_ATTR,
NVME_AEN_CFG_FW_ACT = 1 << NVME_AEN_BIT_FW_ACT,
NVME_AEN_CFG_ANA_CHANGE = 1 << NVME_AEN_BIT_ANA_CHANGE,
--
2.43.7
next prev parent reply other threads:[~2026-11-09 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 12:02 [PATCH 0/2] nvme: make SMART / Health Status AENs reach hwmon alarms Guixin Liu
2026-11-09 12:02 ` Guixin Liu [this message]
2026-11-09 12:09 ` [PATCH 1/2] nvme: define the SMART / Health Status async event bit sashiko-bot
2026-11-09 12:35 ` Guixin Liu
2026-11-09 12:02 ` [PATCH 2/2] nvme-hwmon: notify hwmon alarms on the SMART / Health Status AEN Guixin Liu
2026-11-09 12:19 ` sashiko-bot
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=20261109120207.1352165-2-kanie@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.com \
--cc=sagi@grimberg.me \
/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.