All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhenwei pi <pizhenwei@bytedance.com>
To: kbusch@kernel.org, its@irrelevant.dk, kwolf@redhat.com,
	mreitz@redhat.com
Cc: zhenwei pi <pizhenwei@bytedance.com>,
	philmd@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: [PATCH v4 1/3] block/nvme: introduce bit 5 for critical warning
Date: Fri, 15 Jan 2021 11:27:00 +0800	[thread overview]
Message-ID: <20210115032702.466631-2-pizhenwei@bytedance.com> (raw)
In-Reply-To: <20210115032702.466631-1-pizhenwei@bytedance.com>

According to NVMe spec 1.4 section
<SMART / Health Information (Log Identifier 02h)>, introduce bit 5
for "Persistent Memory Region has become read-only or unreliable".

Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
---
 include/block/nvme.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/include/block/nvme.h b/include/block/nvme.h
index 9494246f1f..0baf4b27cd 100644
--- a/include/block/nvme.h
+++ b/include/block/nvme.h
@@ -789,6 +789,7 @@ enum NvmeSmartWarn {
     NVME_SMART_RELIABILITY            = 1 << 2,
     NVME_SMART_MEDIA_READ_ONLY        = 1 << 3,
     NVME_SMART_FAILED_VOLATILE_MEDIA  = 1 << 4,
+    NVME_SMART_PMR_UNRELIABLE         = 1 << 5,
 };
 
 typedef struct NvmeEffectsLog {
-- 
2.25.1



  reply	other threads:[~2021-01-15  3:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15  3:26 [PATCH v4 0/3] support NVMe smart critial warning injection zhenwei pi
2021-01-15  3:27 ` zhenwei pi [this message]
2021-01-15  9:19   ` [PATCH v4 1/3] block/nvme: introduce bit 5 for critical warning Philippe Mathieu-Daudé
2021-01-15  3:27 ` [PATCH v4 2/3] hw/block/nvme: add smart_critical_warning property zhenwei pi
2021-01-15  3:27 ` [PATCH v4 3/3] hw/blocl/nvme: trigger async event during injecting smart warning zhenwei pi
2021-01-15  9:17   ` Philippe Mathieu-Daudé
2021-01-18  9:34 ` [PATCH v4 0/3] support NVMe smart critial warning injection Klaus Jensen
2021-01-19  2:05   ` zhenwei pi
2021-01-19  5:01     ` Klaus Jensen
2021-01-20  9:21 ` Klaus Jensen

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=20210115032702.466631-2-pizhenwei@bytedance.com \
    --to=pizhenwei@bytedance.com \
    --cc=its@irrelevant.dk \
    --cc=kbusch@kernel.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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.