From: Jason Wang <jasowang@redhat.com>
To: "Eugenio Pérez" <eperezma@redhat.com>
Cc: qemu-devel@nongnu.org, Laurent Vivier <lvivier@redhat.com>,
Dragos Tatulea <dtatulea@nvidia.com>,
si-wei.liu@oracle.com, Parav Pandit <parav@mellanox.com>,
Gautam Dawar <gdawar@xilinx.com>,
Zhu Lingshan <lingshan.zhu@intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>, Cindy Lu <lulu@redhat.com>,
Harpreet Singh Anand <hanand@xilinx.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Hawkins Jiawei <yin31149@gmail.com>,
Shannon Nelson <snelson@pensando.io>,
Lei Yang <leiyang@redhat.com>
Subject: Re: [PATCH v2 5/5] vdpa: remove net cvq migration blocker
Date: Mon, 14 Aug 2023 14:58:13 +0800 [thread overview]
Message-ID: <CACGkMEuWJjE97tFw9HE_4F3n4hEbQTMSfp2q3adXLK6yWoCDCA@mail.gmail.com> (raw)
In-Reply-To: <20230810153611.3410882-6-eperezma@redhat.com>
On Thu, Aug 10, 2023 at 11:36 PM Eugenio Pérez <eperezma@redhat.com> wrote:
>
> Now that we have add migration blockers if the device does not support
> all the needed features, remove the general blocker applied to all net
> devices with CVQ.
>
> Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
Acked-by: Jason Wang <jasowang@redhat.com>
Thanks
> ---
> net/vhost-vdpa.c | 12 ------------
> 1 file changed, 12 deletions(-)
>
> diff --git a/net/vhost-vdpa.c b/net/vhost-vdpa.c
> index 3bf60f9431..6bb56f7d94 100644
> --- a/net/vhost-vdpa.c
> +++ b/net/vhost-vdpa.c
> @@ -1413,18 +1413,6 @@ static NetClientState *net_vhost_vdpa_init(NetClientState *peer,
> s->vhost_vdpa.shadow_vq_ops = &vhost_vdpa_net_svq_ops;
> s->vhost_vdpa.shadow_vq_ops_opaque = s;
> s->cvq_isolated = cvq_isolated;
> -
> - /*
> - * TODO: We cannot migrate devices with CVQ and no x-svq enabled as
> - * there is no way to set the device state (MAC, MQ, etc) before
> - * starting the datapath.
> - *
> - * Migration blocker ownership now belongs to s->vhost_vdpa.
> - */
> - if (!svq) {
> - error_setg(&s->vhost_vdpa.migration_blocker,
> - "net vdpa cannot migrate with CVQ feature");
> - }
> }
> ret = vhost_vdpa_add(nc, (void *)&s->vhost_vdpa, queue_pair_index, nvqs);
> if (ret) {
> --
> 2.39.3
>
prev parent reply other threads:[~2023-08-14 6:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 15:36 [PATCH v2 0/5] Enable vdpa net migration with features depending on CVQ Eugenio Pérez
2023-08-10 15:36 ` [PATCH v2 1/5] vdpa: use first queue SVQ state for CVQ default Eugenio Pérez
2023-08-14 6:57 ` Jason Wang
2023-08-10 15:36 ` [PATCH v2 2/5] vdpa: export vhost_vdpa_set_vring_ready Eugenio Pérez
2023-08-14 6:57 ` Jason Wang
2023-08-10 15:36 ` [PATCH v2 3/5] vdpa: rename vhost_vdpa_net_load to vhost_vdpa_net_cvq_load Eugenio Pérez
2023-08-14 6:57 ` Jason Wang
2023-08-10 15:36 ` [PATCH v2 4/5] vdpa: move vhost_vdpa_set_vrings_ready to the caller Eugenio Pérez
2023-08-14 6:56 ` Jason Wang
2023-08-17 5:41 ` Eugenio Perez Martin
2023-08-22 8:08 ` Eugenio Perez Martin
2023-08-22 8:36 ` Jason Wang
2023-08-10 15:36 ` [PATCH v2 5/5] vdpa: remove net cvq migration blocker Eugenio Pérez
2023-08-14 6:58 ` Jason Wang [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=CACGkMEuWJjE97tFw9HE_4F3n4hEbQTMSfp2q3adXLK6yWoCDCA@mail.gmail.com \
--to=jasowang@redhat.com \
--cc=dtatulea@nvidia.com \
--cc=eperezma@redhat.com \
--cc=gdawar@xilinx.com \
--cc=hanand@xilinx.com \
--cc=leiyang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=lulu@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=parav@mellanox.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=si-wei.liu@oracle.com \
--cc=snelson@pensando.io \
--cc=yin31149@gmail.com \
/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).