[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8b54ca6e948246f1a2bb327bc5cc2c8d8246da58.camel@nvidia.com>
Date: Thu, 10 Aug 2023 09:04:18 +0000
From: Dragos Tatulea <dtatulea@...dia.com>
To: "mst@...hat.com" <mst@...hat.com>
CC: "virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"xuanzhuo@...ux.alibaba.com" <xuanzhuo@...ux.alibaba.com>
Subject: Re: [PATCH 0/2] vdpa/mlx5: Fixes for ASID handling
On Thu, 2023-08-10 at 04:54 -0400, Michael S. Tsirkin wrote:
> On Wed, Aug 02, 2023 at 08:12:16PM +0300, Dragos Tatulea wrote:
> > This patch series is based on Eugenio's fix for handling CVQs in
> > a different ASID [0].
> >
> > The first patch is the actual fix.
> >
> > The next 2 patches are fixing a possible issue that I found while
> > implementing patch 1. The patches are ordered like this for clarity.
> >
> > [0]
> > https://lore.kernel.org/lkml/20230112142218.725622-1-eperezma@redhat.com/
>
>
> So what are we doing with this patchset? If we are merging anything
> for this release it has to happen now.
>
Jason mentioned that wanted an additional cleanup patch to move the cvq specific
code to the net part of mlx5_vdpa. That's quite a refactoring though and would
like to take my time to do an RFC for that first.
It would be good if this got merged now as it fixes an actual problem ...
> > Dragos Tatulea (1):
> > vdpa/mlx5: Fix mr->initialized semantics
> >
> > Eugenio Pérez (1):
> > vdpa/mlx5: Delete control vq iotlb in destroy_mr only when necessary
> >
> > drivers/vdpa/mlx5/core/mlx5_vdpa.h | 2 +
> > drivers/vdpa/mlx5/core/mr.c | 97 +++++++++++++++++++++---------
> > drivers/vdpa/mlx5/net/mlx5_vnet.c | 4 +-
> > 3 files changed, 74 insertions(+), 29 deletions(-)
> >
> > --
> > 2.41.0
>
Powered by blists - more mailing lists