From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Matan Azrad <matan@nvidia.com>
Cc: dev@dpdk.org, stable@dpdk.org, Xueming Li <xuemingl@nvidia.com>
Subject: Re: [PATCH] vdpa/mlx5: workaround queue stop with traffic
Date: Wed, 26 Jan 2022 14:20:48 +0100 [thread overview]
Message-ID: <302ccd65-57ac-5b68-2238-8edbb46d882d@redhat.com> (raw)
In-Reply-To: <20211122131235.3270961-1-matan@nvidia.com>
On 11/22/21 14:12, Matan Azrad wrote:
> When the event thread polls traffic and a virtq is stopping, the FW loses
> synchronization in the virtq indexes.
>
> It causes LM failure on synchronization between the HOST indexes to
> the GUEST indexes.
>
> Unset the event thread before the queue stop in the LM process.
>
> Fixes: 31b9c29c86af ("vdpa/mlx5: support close and config operations")
> Cc: stable@dpdk.org
>
> Signed-off-by: Matan Azrad <matan@nvidia.com>
> Acked-by: Xueming Li <xuemingl@nvidia.com>
> ---
> drivers/vdpa/mlx5/mlx5_vdpa.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/vdpa/mlx5/mlx5_vdpa.c b/drivers/vdpa/mlx5/mlx5_vdpa.c
> index b9e84dd9bf..8dfaba791d 100644
> --- a/drivers/vdpa/mlx5/mlx5_vdpa.c
> +++ b/drivers/vdpa/mlx5/mlx5_vdpa.c
> @@ -250,10 +250,10 @@ mlx5_vdpa_dev_close(int vid)
> DRV_LOG(ERR, "Invalid vDPA device: %s.", vdev->device->name);
> return -1;
> }
> - if (priv->configured)
> - ret |= mlx5_vdpa_lm_log(priv);
> mlx5_vdpa_err_event_unset(priv);
> mlx5_vdpa_cqe_event_unset(priv);
> + if (priv->configured)
> + ret |= mlx5_vdpa_lm_log(priv);
> mlx5_vdpa_steer_unset(priv);
> mlx5_vdpa_virtqs_release(priv);
> mlx5_vdpa_event_qp_global_release(priv);
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2022-01-26 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 13:12 Matan Azrad
2022-01-26 13:20 ` Maxime Coquelin [this message]
2022-01-27 5:10 ` Xia, Chenbo
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=302ccd65-57ac-5b68-2238-8edbb46d882d@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=stable@dpdk.org \
--cc=xuemingl@nvidia.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).