From: "Michael S. Tsirkin" <mst@redhat.com>
To: Dima Stepanov <dimastep@yandex-team.ru>
Cc: kwolf@redhat.com, lvivier@redhat.com, thuth@redhat.com,
qemu-block@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
stefanha@gmail.com, jasowang@redhat.com, qemu-devel@nongnu.org,
mreitz@redhat.com, fengli@smartx.com, yc-core@yandex-team.ru,
pbonzini@redhat.com, raphael.norwitz@nutanix.com,
dgilbert@redhat.com
Subject: Re: [PATCH v5 0/7] vhost-user-blk: fix the migration issue and enhance qtests
Date: Thu, 24 Sep 2020 07:26:14 -0400 [thread overview]
Message-ID: <20200924072506-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <cover.1599813294.git.dimastep@yandex-team.ru>
On Fri, Sep 11, 2020 at 11:39:42AM +0300, Dima Stepanov wrote:
> v4 -> v5:
> - vhost: check queue state in the vhost_dev_set_log routine
> tests/qtest/vhost-user-test: prepare the tests for adding new
> dev class
> tests/qtest/vhost-user-test: add support for the
> vhost-user-blk device
> tests/qtest/vhost-user-test: add migrate_reconnect test
> Reviewed-by: Raphael Norwitz
> - Update qtest, by merging vhost-user-blk "if" case with the
> virtio-blk case.
I dropped patches 3-7 since they were stalling on some systems.
Pls work with Peter Maydell (cc'd) to figure it out.
> v3 -> v4:
> - vhost: recheck dev state in the vhost_migration_log routine
> Reviewed-by: Raphael Norwitz
> - vhost: check queue state in the vhost_dev_set_log routine
> Use "continue" instead of "break" to handle non-initialized
> virtqueue case.
>
> v2 -> v3:
> - update commit message for the
> "vhost: recheck dev state in the vhost_migration_log routine" commit
> - rename "started" field of the VhostUserBlk structure to
> "started_vu", so there will be no confustion with the VHOST started
> field
> - update vhost-user-test.c to always initialize nq local variable
> (spotted by patchew)
>
> v1 -> v2:
> - add comments to connected/started fields in the header file
> - move the "s->started" logic from the vhost_user_blk_disconnect
> routine to the vhost_user_blk_stop routine
>
> Reference e-mail threads:
> - https://lists.gnu.org/archive/html/qemu-devel/2020-05/msg01509.html
> - https://lists.gnu.org/archive/html/qemu-devel/2020-05/msg05241.html
>
> If vhost-user daemon is used as a backend for the vhost device, then we
> should consider a possibility of disconnect at any moment. There was a general
> question here: should we consider it as an error or okay state for the vhost-user
> devices during migration process?
> I think the disconnect event for the vhost-user devices should not break the
> migration process, because:
> - the device will be in the stopped state, so it will not be changed
> during migration
> - if reconnect will be made the migration log will be reinitialized as
> part of reconnect/init process:
> #0 vhost_log_global_start (listener=0x563989cf7be0)
> at hw/virtio/vhost.c:920
> #1 0x000056398603d8bc in listener_add_address_space (listener=0x563989cf7be0,
> as=0x563986ea4340 <address_space_memory>)
> at softmmu/memory.c:2664
> #2 0x000056398603dd30 in memory_listener_register (listener=0x563989cf7be0,
> as=0x563986ea4340 <address_space_memory>)
> at softmmu/memory.c:2740
> #3 0x0000563985fd6956 in vhost_dev_init (hdev=0x563989cf7bd8,
> opaque=0x563989cf7e30, backend_type=VHOST_BACKEND_TYPE_USER,
> busyloop_timeout=0)
> at hw/virtio/vhost.c:1385
> #4 0x0000563985f7d0b8 in vhost_user_blk_connect (dev=0x563989cf7990)
> at hw/block/vhost-user-blk.c:315
> #5 0x0000563985f7d3f6 in vhost_user_blk_event (opaque=0x563989cf7990,
> event=CHR_EVENT_OPENED)
> at hw/block/vhost-user-blk.c:379
> The first patch in the patchset fixes this issue by setting vhost device to the
> stopped state in the disconnect handler and check it the vhost_migration_log()
> routine before returning from the function.
> qtest framework was updated to test vhost-user-blk functionality. The
> vhost-user-blk/vhost-user-blk-tests/migrate_reconnect test was added to reproduce
> the original issue found.
>
> Dima Stepanov (7):
> vhost: recheck dev state in the vhost_migration_log routine
> vhost: check queue state in the vhost_dev_set_log routine
> tests/qtest/vhost-user-test: prepare the tests for adding new dev
> class
> tests/qtest/libqos/virtio-blk: add support for vhost-user-blk
> tests/qtest/vhost-user-test: add support for the vhost-user-blk device
> tests/qtest/vhost-user-test: add migrate_reconnect test
> tests/qtest/vhost-user-test: enable the reconnect tests
>
> hw/block/vhost-user-blk.c | 19 ++-
> hw/virtio/vhost.c | 39 ++++-
> include/hw/virtio/vhost-user-blk.h | 10 ++
> tests/qtest/libqos/virtio-blk.c | 14 +-
> tests/qtest/vhost-user-test.c | 290 +++++++++++++++++++++++++++++++------
> 5 files changed, 322 insertions(+), 50 deletions(-)
>
> --
> 2.7.4
next prev parent reply other threads:[~2020-09-24 11:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 8:39 [PATCH v5 0/7] vhost-user-blk: fix the migration issue and enhance qtests Dima Stepanov
2020-09-11 8:39 ` [PATCH v5 1/7] vhost: recheck dev state in the vhost_migration_log routine Dima Stepanov
2020-09-11 8:39 ` [PATCH v5 2/7] vhost: check queue state in the vhost_dev_set_log routine Dima Stepanov
2020-09-11 8:39 ` [PATCH v5 3/7] tests/qtest/vhost-user-test: prepare the tests for adding new dev class Dima Stepanov
2020-09-11 8:39 ` [PATCH v5 4/7] tests/qtest/libqos/virtio-blk: add support for vhost-user-blk Dima Stepanov
2020-09-15 1:23 ` Raphael Norwitz
2020-09-16 22:13 ` Dima Stepanov
2020-09-21 23:04 ` Raphael Norwitz
2020-09-22 0:54 ` Dima Stepanov
2020-09-11 8:39 ` [PATCH v5 5/7] tests/qtest/vhost-user-test: add support for the vhost-user-blk device Dima Stepanov
2020-09-11 8:39 ` [PATCH v5 6/7] tests/qtest/vhost-user-test: add migrate_reconnect test Dima Stepanov
2020-09-11 8:39 ` [PATCH v5 7/7] tests/qtest/vhost-user-test: enable the reconnect tests Dima Stepanov
2020-09-24 11:26 ` Michael S. Tsirkin [this message]
2020-09-27 6:48 ` [PATCH v5 0/7] vhost-user-blk: fix the migration issue and enhance qtests Dima Stepanov
2020-09-29 7:13 ` Michael S. Tsirkin
2020-09-29 9:48 ` Dima Stepanov
2020-10-07 13:52 ` Dima Stepanov
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=20200924072506-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dgilbert@redhat.com \
--cc=dimastep@yandex-team.ru \
--cc=fengli@smartx.com \
--cc=jasowang@redhat.com \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
--cc=stefanha@gmail.com \
--cc=thuth@redhat.com \
--cc=yc-core@yandex-team.ru \
/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).