From: zhenwei pi <pizhenwei@bytedance.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: axboe@fb.com, linux-nvme@lists.infradead.org, kbusch@kernel.org,
hch@lst.de, linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH 0/3] nvme: enable smart AEN
Date: Wed, 11 May 2022 08:02:11 +0800 [thread overview]
Message-ID: <21bb1776-6ee9-c32d-0049-cd52b14fd133@bytedance.com> (raw)
In-Reply-To: <3c233d71-af16-d230-c207-b9c2ae38afbb@grimberg.me>
On 5/11/22 03:13, Sagi Grimberg wrote:
>
>> Hi,
>>
>> There are several changes in this series:
>> - Add missing NVME_SMART_CRIT_PMR_UNRELIABLE enum type.
>> - Add missing NVME_AEN_CFG_SMART_CRIT_* enum types.
>> - Enable smart AEN.
>
> Is there another side to this patchset? meaning some userland agent
> that listens to these events and does something with these?
I tried to test SMART AEN end to end by QEMU NVMe emulation. I did not
realize that the SMART AEN CFG is not optional.
Also sent this to QEMU(Klaus corrected me):
https://patchwork.kernel.org/project/qemu-devel/cover/20220507072644.263105-1-pizhenwei@bytedance.com/
--
zhenwei pi
prev parent reply other threads:[~2022-05-11 0:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 6:50 zhenwei pi
2022-05-07 6:50 ` [PATCH 1/3] nvme: introduce bit 5 of smart critical warning zhenwei pi
2022-05-10 5:49 ` Christoph Hellwig
2022-05-10 6:44 ` zhenwei pi
2022-05-07 6:50 ` [PATCH 2/3] nvme: introduce smart bits of aen cfg zhenwei pi
2022-05-07 6:50 ` [PATCH 3/3] nvme: enable smart AEN zhenwei pi
2022-05-09 12:41 ` [PATCH 0/3] " zhenwei pi
2022-05-10 19:13 ` Sagi Grimberg
2022-05-11 0:02 ` zhenwei pi [this message]
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=21bb1776-6ee9-c32d-0049-cd52b14fd133@bytedance.com \
--to=pizhenwei@bytedance.com \
--cc=axboe@fb.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®