From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Matan Azrad <matan@nvidia.com>,
dev@dpdk.org, Chenbo Xia <chenbo.xia@intel.com>
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] vdpa/mlx5: fix virtq cleaning
Date: Wed, 24 Mar 2021 11:38:56 +0100 [thread overview]
Message-ID: <56ac6a1a-2641-2fc1-9ae1-75deb0031c16@redhat.com> (raw)
In-Reply-To: <1614595291-112120-1-git-send-email-matan@nvidia.com>
On 3/1/21 11:41 AM, Matan Azrad wrote:
> The HW virtq object can be destroyed ether when the device is closed or
s/ether/either/
> when the state of the virtq becomes disabled.
>
> Some parameters of the virtq should continue to be managed when the
> virtq state is changed but all of them must be initialized when the
> device is closed.
>
> Wrongly, the enable parameter stayed on when the device is closed what
> might cause creation of invalid virtq in the next time a device is
> assigned to the driver.
>
> Clean all the virtqs memory when the device is closed.
>
> Fixes: c47d6e83334e ("vdpa/mlx5: support queue update")
> Cc: stable@dpdk.org
>
> Signed-off-by: Matan Azrad <matan@nvidia.com>
> Acked-by: Xueming Li <xuemingl@nvidia.com>
> ---
> drivers/vdpa/mlx5/mlx5_vdpa_virtq.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/vdpa/mlx5/mlx5_vdpa_virtq.c b/drivers/vdpa/mlx5/mlx5_vdpa_virtq.c
> index ef2642a..024c5c4 100644
> --- a/drivers/vdpa/mlx5/mlx5_vdpa_virtq.c
> +++ b/drivers/vdpa/mlx5/mlx5_vdpa_virtq.c
> @@ -103,13 +103,8 @@
> for (i = 0; i < priv->nr_virtqs; i++) {
> virtq = &priv->virtqs[i];
> mlx5_vdpa_virtq_unset(virtq);
> - if (virtq->counters) {
> + if (virtq->counters)
> claim_zero(mlx5_devx_cmd_destroy(virtq->counters));
> - virtq->counters = NULL;
> - memset(&virtq->reset, 0, sizeof(virtq->reset));
> - }
> - memset(virtq->err_time, 0, sizeof(virtq->err_time));
> - virtq->n_retry = 0;
> }
> for (i = 0; i < priv->num_lag_ports; i++) {
> if (priv->tiss[i]) {
> @@ -126,6 +121,7 @@
> priv->virtq_db_addr = NULL;
> }
> priv->features = 0;
> + memset(priv->virtqs, 0, sizeof(*virtq) * priv->nr_virtqs);
> priv->nr_virtqs = 0;
> }
>
>
With typo fixed in commit message:
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
No need to resubmit, we can fix the typo while applying.
Thanks,
Maxime
next prev parent reply other threads:[~2021-03-24 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 10:41 Matan Azrad
2021-03-24 10:38 ` Maxime Coquelin [this message]
2021-03-31 8:46 ` 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=56ac6a1a-2641-2fc1-9ae1-75deb0031c16@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=stable@dpdk.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).