From: Stefano Garzarella <sgarzare@redhat.com>
To: Eugenio Perez Martin <eperezma@redhat.com>
Cc: qemu-devel@nongnu.org, alvaro.karsz@solid-run.com,
Laurent Vivier <lvivier@redhat.com>,
Gautam Dawar <gdawar@xilinx.com>,
Jason Wang <jasowang@redhat.com>,
Harpreet Singh Anand <hanand@xilinx.com>,
Zhu Lingshan <lingshan.zhu@intel.com>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Eli Cohen <eli@mellanox.com>,
si-wei.liu@oracle.com, longpeng2@huawei.com,
Cindy Lu <lulu@redhat.com>, Parav Pandit <parav@mellanox.com>,
Liuxiangdong <liuxiangdong5@huawei.com>,
Shannon Nelson <snelson@pensando.io>,
Lei Yang <leiyang@redhat.com>
Subject: Re: [RFC PATCH for 8.1 5/6] vdpa: move CVQ isolation check to net_init_vhost_vdpa
Date: Thu, 23 Mar 2023 09:32:18 +0100 [thread overview]
Message-ID: <20230323083218.4xqix24clzigc564@sgarzare-redhat> (raw)
In-Reply-To: <CAJaqyWdaXCO5VDSQ_wda9rCFH0VHcTMEuq4RP2b-LLGFty7m7g@mail.gmail.com>
On Wed, Mar 22, 2023 at 07:04:03PM +0100, Eugenio Perez Martin wrote:
>On Wed, Mar 22, 2023 at 3:27 PM Stefano Garzarella <sgarzare@redhat.com> wrote:
>>
>> On Fri, Mar 17, 2023 at 03:55:41PM +0100, Eugenio Pérez wrote:
>> >Evaluating it at start time instead of initialization time may make the
>> >guest capable of dynamically adding or removing migration blockers.
>> >
>> >Also, moving to initialization reduces the number of ioctls in the
>> >migration, reducing failure possibilities.
>> >
>> >Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
>> >---
>> > net/vhost-vdpa.c | 200 +++++++++++++++++++++++++++++++++++++----------
>> > 1 file changed, 157 insertions(+), 43 deletions(-)
>> >
>> >diff --git a/net/vhost-vdpa.c b/net/vhost-vdpa.c
>> >index 4397c0d4b3..818a24fb0e 100644
>> >--- a/net/vhost-vdpa.c
>> >+++ b/net/vhost-vdpa.c
>> >@@ -43,6 +43,13 @@ typedef struct VhostVDPAState {
>> >
>> > /* The device always have SVQ enabled */
>> > bool always_svq;
>> >+
>> >+ /* The device can isolate CVQ in its own ASID if MQ is negotiated */
>> >+ bool cvq_isolated_mq;
>> >+
>> >+ /* The device can isolate CVQ in its own ASID if MQ is not negotiated */
>> >+ bool cvq_isolated;
>> >+
>>
>> I am not familiar with how CVQ works, so my question might be trivial
>> ;-) but why do we need to have 2 variables depending on F_MQ?
>>
>
>You're right, it is not specified anywhere in the series.
>
>Vring ASID / group management is based on vq indexes. CVQ is always
>the last queue, but its position depends on MQ. If it is not acked,
>cvq will always be queue #2. if it is acked, it will be
>net_config->max_virtqueue_pairs*2.
>
>Previously this was done at device start, so we always know if mq has
>been acked or not. But now we are moving to initialization, so we need
>to probe both configurations.
>
>Is that clearer now? I'll add to the patch description for sure.
Yes, thanks for the explanation!
Stefano
next prev parent reply other threads:[~2023-03-23 8:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 14:55 [RFC PATCH for 8.1 0/6] Move ASID test to vhost-vdpa net initialization Eugenio Pérez
2023-03-17 14:55 ` [RFC PATCH for 8.1 1/6] vdpa: Remove status in reset tracing Eugenio Pérez
2023-03-22 14:22 ` Stefano Garzarella
2023-03-22 15:46 ` Eugenio Perez Martin
2023-03-17 14:55 ` [RFC PATCH for 8.1 2/6] vdpa: add vhost_vdpa_reset_status_fd Eugenio Pérez
2023-03-22 14:24 ` Stefano Garzarella
2023-03-22 17:36 ` Eugenio Perez Martin
2023-03-23 8:28 ` Stefano Garzarella
2023-03-17 14:55 ` [RFC PATCH for 8.1 3/6] vdpa: add vhost_vdpa_set_dev_features_fd Eugenio Pérez
2023-03-22 14:25 ` Stefano Garzarella
2023-03-17 14:55 ` [RFC PATCH for 8.1 4/6] vdpa: return errno in vhost_vdpa_get_vring_group error Eugenio Pérez
2023-03-22 14:26 ` Stefano Garzarella
2023-03-22 17:38 ` Eugenio Perez Martin
2023-03-23 8:30 ` Stefano Garzarella
2023-03-17 14:55 ` [RFC PATCH for 8.1 5/6] vdpa: move CVQ isolation check to net_init_vhost_vdpa Eugenio Pérez
2023-03-22 14:27 ` Stefano Garzarella
2023-03-22 18:04 ` Eugenio Perez Martin
2023-03-23 8:32 ` Stefano Garzarella [this message]
2023-03-17 14:55 ` [RFC PATCH for 8.1 6/6] vdpa: Cache cvq group in VhostVDPAState Eugenio Pérez
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=20230323083218.4xqix24clzigc564@sgarzare-redhat \
--to=sgarzare@redhat.com \
--cc=alvaro.karsz@solid-run.com \
--cc=arei.gonglei@huawei.com \
--cc=eli@mellanox.com \
--cc=eperezma@redhat.com \
--cc=gdawar@xilinx.com \
--cc=hanand@xilinx.com \
--cc=jasowang@redhat.com \
--cc=leiyang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=liuxiangdong5@huawei.com \
--cc=longpeng2@huawei.com \
--cc=lulu@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=parav@mellanox.com \
--cc=qemu-devel@nongnu.org \
--cc=si-wei.liu@oracle.com \
--cc=snelson@pensando.io \
/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).