From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: zhenwei pi <pizhenwei@bytedance.com>,
kbusch@kernel.org, its@irrelevant.dk, kwolf@redhat.com,
mreitz@redhat.com
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH v4 3/3] hw/blocl/nvme: trigger async event during injecting smart warning
Date: Fri, 15 Jan 2021 10:17:20 +0100 [thread overview]
Message-ID: <2aaa4523-eddf-1246-b48b-f0a0f0daf582@redhat.com> (raw)
In-Reply-To: <20210115032702.466631-4-pizhenwei@bytedance.com>
On 1/15/21 4:27 AM, zhenwei pi wrote:
> During smart critical warning injection by setting property from QMP
> command, also try to trigger asynchronous event.
>
> Suggested by Keith, if a event has already been raised, there is no
> need to enqueue the duplicate event any more.
>
> Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
> ---
> hw/block/nvme.c | 48 +++++++++++++++++++++++++++++++++++++-------
> include/block/nvme.h | 1 +
> 2 files changed, 42 insertions(+), 7 deletions(-)
Typo "blocl" in subject ;) No need to repost.
next prev parent reply other threads:[~2021-01-15 9:19 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 ` [PATCH v4 1/3] block/nvme: introduce bit 5 for critical warning zhenwei pi
2021-01-15 9:19 ` 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é [this message]
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=2aaa4523-eddf-1246-b48b-f0a0f0daf582@redhat.com \
--to=philmd@redhat.com \
--cc=its@irrelevant.dk \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pizhenwei@bytedance.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.