From: Minwoo Im <minwoo.im.dev@gmail.com>
To: Keith Busch <kbusch@kernel.org>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: Klaus Jensen <its@irrelevant.dk>, Kevin Wolf <kwolf@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH 2/2] hw/block/nvme: add 'nvme_ana_inject_state' HMP command
Date: Fri, 26 Feb 2021 22:16:51 +0900 [thread overview]
Message-ID: <20210226131651.GB11808@localhost.localdomain> (raw)
In-Reply-To: <20210214112400.26956-3-minwoo.im.dev@gmail.com>
On 21-02-14 20:24:00, Minwoo Im wrote:
> Human Monitor Interface(HMP) is there for easy human debugging. This
> patch added a HMP command 'nvme_ana_inject_state'. This can be executed
> from the QEMU monitor. This command will have the following syntax:
>
> # nvme_ana_inject_state <nvme-id> <anagrpid> <state>
> (qemu) nvme_ana_inject_state nvme0 1 inaccessible
>
> The example above will make ANA group #1 transitioned to
> ANA_INACCESSIBLE state for `nvme0` controller device. Additionally,
> device will notify to the host that ANA has been changed via
> Asynchronous Event Notifier(AEN). Then the host will figure out another
> path to I/O for the namespace by reading the log page for ANA
> information again, and this is what we call the multipath I/O.
>
> This feature is good to debug the host multipath I/O by controlling the
> device ANA group state transition. The path-related errors can be
> tested and debugged by this feature. Also, the HMP command interafce
> will make us not to build QEMU itself again to control things in device.
>
> This interface supports Persistent Loss state transition, but it's not
> going to be persistent: volatile of qemu perspective.
>
> Cc: Dr . David Alan Gilbert <dgilbert@redhat.com>
> Signed-off-by: Minwoo Im <minwoo.im.dev@gmail.com>
Hello Keith,
Do you have any comments about this injection method? As discussed
ealier, I've tried to introduce a natural way to control some of device
status like ANA state which device can behave properly.
It would be great if I can have your feedback on this :)
Thanks!
prev parent reply other threads:[~2021-02-26 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 11:23 [PATCH 0/2] hw/block/nvme: support ANA Minwoo Im
2021-02-14 11:23 ` [PATCH 1/2] hw/block/nvme: support Asymmetric Namespace Access(ANA) Minwoo Im
2021-02-14 11:24 ` [PATCH 2/2] hw/block/nvme: add 'nvme_ana_inject_state' HMP command Minwoo Im
2021-02-26 13:16 ` Minwoo Im [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=20210226131651.GB11808@localhost.localdomain \
--to=minwoo.im.dev@gmail.com \
--cc=dgilbert@redhat.com \
--cc=its@irrelevant.dk \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mreitz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).