summaryrefslogtreecommitdiffstats
path: root/drivers/vdpa/mlx5/net/main.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* vdpa/mlx5: Connect mlx5_vdpa to auxiliary busLeon Romanovsky2020-12-061-76/+0
| | | | | | | Change module registration logic to use auxiliary bus instead of custom made mlx5 register interface. Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
* vdpa/mlx5: Make hardware definitions visible to all mlx5 devicesLeon Romanovsky2020-12-041-1/+1
| | | | | | | | | | | | Move mlx5_vdpa IFC header file to the general include folder, so mlx5_core will be able to reuse it to check if VDPA is supported prior to creating an auxiliary device. As part of this move, update the header file name to mlx5 general naming scheme. Reviewed-by: Parav Pandit <parav@nvidia.com> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
* vdpa/mlx5: Add VDPA driver for supported mlx5 devicesEli Cohen2020-08-061-0/+76
Add a front end VDPA driver that registers in the VDPA bus and provides networking to a guest. The VDPA driver creates the necessary resources on the VF it is driving such that data path will be offloaded. Notifications are being communicated through the driver. Currently, only VFs are supported. In subsequent patches we will have devlink support to control which VF is used for VDPA and which function is used for regular networking. Reviewed-by: Parav Pandit <parav@mellanox.com> Signed-off-by: Eli Cohen <eli@mellanox.com> Link: https://lore.kernel.org/r/20200804162048.22587-13-eli@mellanox.com Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Acked-by: Jason Wang <jasowang@redhat.com>