diff options
author | Dragos Tatulea | 2023-12-25 17:12:02 +0200 |
---|---|---|
committer | Michael S. Tsirkin | 2024-01-10 13:01:38 -0500 |
commit | a06bd11b18fdf2d40e2b81d4318abc6cc38e70c9 (patch) | |
tree | acb32de6383f206e9b261de76798197d9eb7b2f6 /mm/memblock.c | |
parent | f756dd3e2a4c704c0ab5ecb143ab71f1249af497 (diff) |
vdpa/mlx5: Introduce reference counting to mrs
Deleting the old mr during mr update (.set_map) and then modifying the
vqs with the new mr is not a good flow for firmware. The firmware
expects that mkeys are deleted after there are no more vqs referencing
them.
Introduce reference counting for mrs to fix this. It is the only way to
make sure that mkeys are not in use by vqs.
An mr reference is taken when the mr is associated to the mr asid table
and when the mr is linked to the vq on create/modify. The reference is
released when the mkey is unlinked from the vq (trough modify/destroy)
and from the mr asid table.
To make things consistent, get rid of mlx5_vdpa_destroy_mr and use
get/put semantics everywhere.
Reviewed-by: Gal Pressman <gal@nvidia.com>
Acked-by: Eugenio PĂ©rez <eperezma@redhat.com>
Acked-by: Jason Wang <jasowang@redhat.com>
Signed-off-by: Dragos Tatulea <dtatulea@nvidia.com>
Message-Id: <20231225151203.152687-8-dtatulea@nvidia.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'mm/memblock.c')
0 files changed, 0 insertions, 0 deletions