From: Li Feng <fengli@smartx.com>
To: "Markus Armbruster" <armbru@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Raphael Norwitz" <raphael.norwitz@nutanix.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Fam Zheng" <fam@euphon.net>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
qemu-block@nongnu.org (open list:Block layer core),
qemu-devel@nongnu.org (open list:All patches CC here)
Cc: Li Feng <fengli@smartx.com>
Subject: [PATCH v7 0/5] Implement reconnect for vhost-user-scsi
Date: Sun, 8 Oct 2023 17:12:00 +0800 [thread overview]
Message-ID: <20231008091220.870171-1-fengli@smartx.com> (raw)
Changes for v7:
- [PATCH 3/5] vhost-user-scsi: support reconnect to backend
- Add reporting the error in vhost-scsi;
- Rebase to master and fix the conflict.
- Add "Reviewed-by" tags.
Changes for v6:
- [PATCH] vhost-user: fix lost reconnect
- Fix missing assign event_cb.
Changes for v5:
- No logic has been changed, just move part of the code from patch 4 to patch 5.
Changes for v4:
- Merge
https://lore.kernel.org/all/20230830045722.611224-1-fengli@smartx.com/ to
this series.
- Add ERRP_GUARD in vhost_user_scsi_realize;
- Reword the commit messages.
Changes for v3:
- Split the vhost_user_scsi_handle_output to a separate patch;
- Move the started_vu from vhost scsi common header to vhost-user-scsi header;
- Fix a log print error;
Changes for v2:
- Split the v1 patch to small separate patchset;
- New patch for fixing fd leak, which has sent to reviewers in another
mail;
- Implement the `vhost_user_scsi_handle_output`;
- Add the started_vu safe check;
- Fix error handler;
- Check the inflight before set/get inflight fd.
Li Feng (5):
vhost-user-common: send get_inflight_fd once
vhost: move and rename the conn retry times
vhost-user-scsi: support reconnect to backend
vhost-user-scsi: start vhost when guest kicks
vhost-user: fix lost reconnect
hw/block/vhost-user-blk.c | 6 +-
hw/scsi/vhost-scsi-common.c | 47 ++---
hw/scsi/vhost-scsi.c | 6 +-
hw/scsi/vhost-user-scsi.c | 253 +++++++++++++++++++++++---
hw/virtio/vhost-user-gpio.c | 5 +-
hw/virtio/vhost-user.c | 10 +-
include/hw/virtio/vhost-scsi-common.h | 2 +-
include/hw/virtio/vhost-user-scsi.h | 4 +
include/hw/virtio/vhost-user.h | 3 +-
include/hw/virtio/vhost.h | 2 +
10 files changed, 278 insertions(+), 60 deletions(-)
--
2.41.0
next reply other threads:[~2023-10-08 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 9:12 Li Feng [this message]
2023-10-08 9:12 ` [PATCH v7 1/5] vhost-user-common: send get_inflight_fd once Li Feng
2023-10-08 9:12 ` [PATCH v7 2/5] vhost: move and rename the conn retry times Li Feng
2023-10-08 9:12 ` [PATCH v7 3/5] vhost-user-scsi: support reconnect to backend Li Feng
2023-10-08 10:46 ` Manos Pitsidianakis
2023-10-09 4:34 ` Li Feng
2023-10-08 9:12 ` [PATCH v7 4/5] vhost-user-scsi: start vhost when guest kicks Li Feng
2023-10-08 9:12 ` [PATCH v7 5/5] vhost-user: fix lost reconnect Li Feng
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=20231008091220.870171-1-fengli@smartx.com \
--to=fengli@smartx.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
--cc=viresh.kumar@linaro.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).