[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v4 0/3] support NVMe smart critial warning injection
From: |
Klaus Jensen |
Subject: |
Re: [PATCH v4 0/3] support NVMe smart critial warning injection |
Date: |
Wed, 20 Jan 2021 10:21:46 +0100 |
On Jan 15 11:26, zhenwei pi wrote:
> v3 -> v4:
> - Drop "Fix overwritten bar.cap". (Already fixed)
>
> - Avoid to enqueue the duplicate event.
>
> - Several minor changes for coding style & function/variable name.
>
> v2 -> v3:
> - Introduce "Persistent Memory Region has become read-only or
> unreliable"
>
> - Fix overwritten bar.cap
>
> - Check smart critical warning value from QOM.
>
> - Trigger asynchronous event during smart warning injection.
>
> v1 -> v2:
> - Suggested by Philippe & Klaus, set/get smart_critical_warning by QMP.
>
> v1:
> - Add smart_critical_warning for nvme device which can be set by QEMU
> command line to emulate hardware error.
>
> Zhenwei Pi (3):
> block/nvme: introduce bit 5 for critical warning
> hw/block/nvme: add smart_critical_warning property
> hw/blocl/nvme: trigger async event during injecting smart warning
>
> hw/block/nvme.c | 91 +++++++++++++++++++++++++++++++++++++++-----
> hw/block/nvme.h | 1 +
> include/block/nvme.h | 3 ++
> 3 files changed, 86 insertions(+), 9 deletions(-)
>
Thanks! Applied to nvme-next.
signature.asc
Description: PGP signature