From: Raphael Norwitz <raphael.norwitz@nutanix.com>
To: Li Feng <fengli@smartx.com>
Cc: "Michael S. Tsirkin" <mst@redhat.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>,
"open list:Block layer core" <qemu-block@nongnu.org>,
"open list:All patches CC here" <qemu-devel@nongnu.org>
Subject: Re: [PATCH 2/2] vhost-user-scsi: free the inflight area when reset
Date: Tue, 28 Nov 2023 05:57:47 +0000 [thread overview]
Message-ID: <530BAC1B-120F-42CF-802C-6A29DCB980ED@nutanix.com> (raw)
In-Reply-To: <20231123055431.217792-3-fengli@smartx.com>
> On Nov 23, 2023, at 12:54 AM, Li Feng <fengli@smartx.com> wrote:
>
> Keep it the same to vhost-user-blk.
> At the same time, fix the vhost_reset_device.
>
> Signed-off-by: Li Feng <fengli@smartx.com>
Reviewed-by: Raphael Norwitz <raphael.norwitz@nutanix.com>
> ---
> hw/scsi/vhost-user-scsi.c | 16 ++++++++++++++++
> hw/virtio/virtio.c | 2 +-
> 2 files changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/hw/scsi/vhost-user-scsi.c b/hw/scsi/vhost-user-scsi.c
> index 2060f9f94b..780f10559d 100644
> --- a/hw/scsi/vhost-user-scsi.c
> +++ b/hw/scsi/vhost-user-scsi.c
> @@ -360,6 +360,20 @@ static Property vhost_user_scsi_properties[] = {
> DEFINE_PROP_END_OF_LIST(),
> };
>
> +static void vhost_user_scsi_reset(VirtIODevice *vdev)
> +{
> + VHostUserSCSI *s = VHOST_USER_SCSI(vdev);
> + VHostSCSICommon *vsc = VHOST_SCSI_COMMON(s);
> +
> + vhost_dev_free_inflight(vsc->inflight);
> +}
> +
> +static struct vhost_dev *vhost_user_scsi_get_vhost(VirtIODevice *vdev)
> +{
> + VHostSCSICommon *vsc = VHOST_SCSI_COMMON(vdev);
> + return &vsc->dev;
> +}
> +
> static const VMStateDescription vmstate_vhost_scsi = {
> .name = "virtio-scsi",
> .minimum_version_id = 1,
> @@ -385,6 +399,8 @@ static void vhost_user_scsi_class_init(ObjectClass *klass, void *data)
> vdc->set_config = vhost_scsi_common_set_config;
> vdc->set_status = vhost_user_scsi_set_status;
> fwc->get_dev_path = vhost_scsi_common_get_fw_dev_path;
> + vdc->reset = vhost_user_scsi_reset;
> + vdc->get_vhost = vhost_user_scsi_get_vhost;
> }
>
> static void vhost_user_scsi_instance_init(Object *obj)
> diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
> index 4259fefeb6..d0a640af63 100644
> --- a/hw/virtio/virtio.c
> +++ b/hw/virtio/virtio.c
> @@ -2137,7 +2137,7 @@ void virtio_reset(void *opaque)
> vdev->device_endian = virtio_default_endian();
> }
>
> - if (vdev->vhost_started) {
> + if (vdev->vhost_started && k->get_vhost) {
> vhost_reset_device(k->get_vhost(vdev));
> }
>
> --
> 2.42.0
>
prev parent reply other threads:[~2023-11-28 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 5:54 [PATCH 0/2] fix some vhost-user issues Li Feng
2023-11-23 5:54 ` [PATCH 1/2] vhost-user: fix the reconnect error Li Feng
2023-11-28 5:57 ` Raphael Norwitz
2023-11-23 5:54 ` [PATCH 2/2] vhost-user-scsi: free the inflight area when reset Li Feng
2023-11-28 5:57 ` Raphael Norwitz [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=530BAC1B-120F-42CF-802C-6A29DCB980ED@nutanix.com \
--to=raphael.norwitz@nutanix.com \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--cc=fengli@smartx.com \
--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=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).