From: David Marchand <david.marchand@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, chenbox@nvidia.com, schalla@marvell.com
Subject: Re: [PATCH v2 0/2] net/virtio: vhost-vdpa fixes
Date: Wed, 13 Mar 2024 15:48:50 +0100 [thread overview]
Message-ID: <CAJFAV8zTKRK+1dqg6j3WaAW_bvt1pGM5NAperbdY=WwJja5UTg@mail.gmail.com> (raw)
In-Reply-To: <20240313125932.1878279-1-maxime.coquelin@redhat.com>
On Wed, Mar 13, 2024 at 1:59 PM Maxime Coquelin
<maxime.coquelin@redhat.com> wrote:
>
> While investigating vhost-vdpa initialization issue with mlx5
> vDPA, we found two issues fixed by following patches.
>
> In this v2, the control queue issue mentioned in v1 is
> fixed. It turned out to the control queue being enabled
> only if multiqueue was negotiated. It is fixed by enabling
> it at device startup, and disabling it at stop time.
>
> We still have an issue on one of our setup with mlx5, where
> the mlx5 device sets VIRTIO_CONFIG_S_FAILED status, it is
> currently being investigated.
v2 is working fine on my system, what else matters? :-)
The current fixes in this series make sense.
We may do followup fixes in the next release.
>
> Changes in v2:
> --------------
> - Fix cvq enablement
> - Fix typo in commit message (David)
>
>
> Maxime Coquelin (2):
> net/virtio: fix vDPA device init advertising control queue
> net/virtio: fix notification area initialization
>
> .../net/virtio/virtio_user/virtio_user_dev.c | 27 +++++++++++++------
> 1 file changed, 19 insertions(+), 8 deletions(-)
>
Series applied, thanks.
--
David Marchand
prev parent reply other threads:[~2024-03-13 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 12:59 Maxime Coquelin
2024-03-13 12:59 ` [PATCH v2 1/2] net/virtio: fix vDPA device init advertising control queue Maxime Coquelin
2024-03-13 14:12 ` David Marchand
2024-03-13 12:59 ` [PATCH v2 2/2] net/virtio: fix notification area initialization Maxime Coquelin
2024-03-13 14:48 ` David Marchand [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='CAJFAV8zTKRK+1dqg6j3WaAW_bvt1pGM5NAperbdY=WwJja5UTg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=schalla@marvell.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).