search for: 6f5312f80183

Displaying 3 results from an estimated 3 matches for "6f5312f80183".

2023 Aug 16
1
[PATCH RFC 4/4] vhost-vdpa: introduce IOTLB_PERSIST backend feature bit
...y been decoupled > > from the vdpa reset. > Not in the sense of API, it' been coupled since day one from the > implementations of every on-chip IOMMU parent driver, namely mlx5_vdpa > and vdpa_sim. Because of that, later on the (improper) support for > virtio-vdpa, from commit 6f5312f80183 ("vdpa/mlx5: Add support for > running with virtio_vdpa") and 6c3d329e6486 ("vdpa_sim: get rid of DMA > ops") misused the .reset() op to realize 1:1 mapping, rendering strong > coupling between device reset and reset of iotlb mappings. This series > try to rectify th...
2023 Aug 16
1
[PATCH RFC 4/4] vhost-vdpa: introduce IOTLB_PERSIST backend feature bit
...t;>> from the vdpa reset. >> Not in the sense of API, it' been coupled since day one from the >> implementations of every on-chip IOMMU parent driver, namely mlx5_vdpa >> and vdpa_sim. Because of that, later on the (improper) support for >> virtio-vdpa, from commit 6f5312f80183 ("vdpa/mlx5: Add support for >> running with virtio_vdpa") and 6c3d329e6486 ("vdpa_sim: get rid of DMA >> ops") misused the .reset() op to realize 1:1 mapping, rendering strong >> coupling between device reset and reset of iotlb mappings. This series >> t...
2023 Aug 22
1
[PATCH RFC 4/4] vhost-vdpa: introduce IOTLB_PERSIST backend feature bit
...vdpa reset. > >> Not in the sense of API, it' been coupled since day one from the > >> implementations of every on-chip IOMMU parent driver, namely mlx5_vdpa > >> and vdpa_sim. Because of that, later on the (improper) support for > >> virtio-vdpa, from commit 6f5312f80183 ("vdpa/mlx5: Add support for > >> running with virtio_vdpa") and 6c3d329e6486 ("vdpa_sim: get rid of DMA > >> ops") misused the .reset() op to realize 1:1 mapping, rendering strong > >> coupling between device reset and reset of iotlb mappings. This se...