From: Erwan Velu <erwanaliasr1@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Erwan Velu <e.velu@criteo.com>, Keith Busch <kbusch@kernel.org>,
Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org (open list:NVM EXPRESS DRIVER),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH] nvme: Report model,sn,fw,pci device information during init
Date: Wed, 15 Jun 2022 20:02:13 +0200 [thread overview]
Message-ID: <20220615180213.760756-1-e.velu@criteo.com> (raw)
SCSI-based device get their identify properties being printed when initialized like :
[ 1.245357] scsi 0:0:0:0: Direct-Access ATA HGST HTE721010A9 A3M0 PQ: 0 ANSI: 5
When initializing nvme devices, no identification message is reported
making difficult to identify them during the boot process. If the system
crashes during boot process or if the init phase fail, it could be very diffcult
to identify the faulty disk.
This patch reports model, serial, firmware version and pci information
as soon as possible making this early identifying task possible.
Reporting the serial has the interest of being able to ensure which
physical drive is concerned if a hardware replacement is required and
host features the exact same drive multiple times.
A typical output looks like:
[ 0.383353] nvme nvme0: pci function 0000:00:03.0
[ 0.418184] nvme nvme0: MODEL:QEMU NVMe Ctrl SN:deadbeef FW:1.0 PCI_ID:1b36:1af4
[ 0.422020] nvme nvme0: 1/0/0 default/read/poll queues
Signed-off-by: Erwan Velu <e.velu@criteo.com>
---
drivers/nvme/host/core.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index 24165daee3c8..0922b7a470b1 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -2987,6 +2987,14 @@ static int nvme_init_identify(struct nvme_ctrl *ctrl)
if (!ctrl->identified) {
unsigned int i;
+ /* Reporting model, serial, firmware and pci info */
+ dev_info(ctrl->device, "MODEL:%.*s SN:%.*s FW:%.*s PCI_ID:%04x:%04x\n",
+ (int)sizeof(id->mn), id->mn,
+ (int)sizeof(id->sn),id->sn,
+ (int)sizeof(id->fr), id->fr,
+ le16_to_cpu(id->vid),
+ le16_to_cpu(id->ssvid));
+
ret = nvme_init_subsystem(ctrl, id);
if (ret)
goto out_free;
--
2.35.3
next reply other threads:[~2022-06-15 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 18:02 Erwan Velu [this message]
2022-06-15 18:41 ` Keith Busch
2022-06-15 18:52 ` Erwan Velu
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=20220615180213.760756-1-e.velu@criteo.com \
--to=erwanaliasr1@gmail.com \
--cc=axboe@fb.com \
--cc=e.velu@criteo.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--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 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®