[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230112142218.725622-2-eperezma@redhat.com>
Date: Thu, 12 Jan 2023 15:22:16 +0100
From: Eugenio Pérez <eperezma@...hat.com>
To: mst@...hat.com, elic@...dia.com
Cc: linux-kernel@...r.kernel.org, parav@...dia.com, lulu@...hat.com,
jasowang@...hat.com, virtualization@...ts.linux-foundation.org,
sgarzare@...hat.com, si-wei.liu@...cle.com
Subject: [RFC 1/3] vdpa/mlx5: reset iotlb at dup_iotlb
Regular memory region changes already reset cvq iotlb at set_map.
However this is not true if CVQ and data VQs are in different ASID.
Clean the CVQ iotlb every time we hit dup_iotlb.
Fixes: 8fcd20c30704 ("vdpa/mlx5: Support different address spaces for control and data")
Signed-off-by: Eugenio Pérez <eperezma@...hat.com>
---
drivers/vdpa/mlx5/core/mr.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/vdpa/mlx5/core/mr.c b/drivers/vdpa/mlx5/core/mr.c
index 0a1e0b0dc37e..ae34dcac9a3f 100644
--- a/drivers/vdpa/mlx5/core/mr.c
+++ b/drivers/vdpa/mlx5/core/mr.c
@@ -456,6 +456,8 @@ static int dup_iotlb(struct mlx5_vdpa_dev *mvdev, struct vhost_iotlb *src)
u64 start = 0, last = ULLONG_MAX;
int err;
+ vhost_iotlb_reset(mvdev->cvq.iotlb);
+
if (!src) {
err = vhost_iotlb_add_range(mvdev->cvq.iotlb, start, last, start, VHOST_ACCESS_RW);
return err;
--
2.31.1
Powered by blists - more mailing lists