linux-toradex.git/include/linux/mlx4/device.h, branch v5.17-rc1

mlx4: constify args for const dev_addr

2021-10-05T12:15:35+00:00

netdev->dev_addr will become const soon. Make sure all
functions which pass it around mark appropriate args
as const.

Signed-off-by: Jakub Kicinski 
Reviewed-by: Tariq Toukan 
Signed-off-by: David S. Miller

RDMA/mlx4: Do not map the core_clock page to user space unless enabled

2021-06-03T17:19:53+00:00

Currently when mlx4 maps the hca_core_clock page to the user space there
are read-modifiable registers, one of which is semaphore, on this page as
well as the clock counter. If user reads the wrong offset, it can modify
the semaphore and hang the device.

Do not map the hca_core_clock page to the user space unless the device has
been put in a backwards compatibility mode to support this feature.

After this patch, mlx4 core_clock won't be mapped to user space on the
majority of existing devices and the uverbs device time feature in
ibv_query_rt_values_ex() will be disabled.

Fixes: 52033cfb5aab ("IB/mlx4: Add mmap call to map the hardware clock")
Link: https://lore.kernel.org/r/9632304e0d6790af84b3b706d8c18732bc0d5e27.1622726305.git.leonro@nvidia.com
Signed-off-by: Shay Drory 
Signed-off-by: Leon Romanovsky 
Signed-off-by: Jason Gunthorpe

net/mlx4: Remove unused #define MAX_MSIX_P_PORT

2020-12-08T02:22:35+00:00

All usages of the definition MAX_MSIX_P_PORT were removed.
It's not in use anymore. Remove it.

Signed-off-by: Tariq Toukan 
Reviewed-by: Moshe Shemesh 
Link: https://lore.kernel.org/r/20201206091254.12476-1-tariqt@nvidia.com
Signed-off-by: Jakub Kicinski

RDMA/mlx4: Remove FMR support for memory registration

2020-06-02T23:32:54+00:00

HCA's that are driven by mlx4 driver support FRWR method to register
memory. Remove the ancient and unsafe FMR method.

Link: https://lore.kernel.org/r/8-v3-f58e6669d5d3+2cf-fmr_removal_jgg@mellanox.com
Reviewed-by: Max Gurtovoy 
Signed-off-by: Max Gurtovoy 
Signed-off-by: Jason Gunthorpe

mlx4: Bump up MAX_MSIX from 64 to 128

2020-01-12T20:32:32+00:00

On modern hardware with a large number of cpus and using XDP,
the current MSIX limit is insufficient.  Bump the limit in
order to allow more queues.

Signed-off-by: Jonathan Lemon 
Reviewed-by: Jack Wang 
Reviewed-by: Tariq Toukan 
Signed-off-by: Jakub Kicinski

{net, IB}/mlx4: Initialize CQ buffers in the driver when possible

2018-11-22T19:38:36+00:00

Perform CQ initialization in the driver when the capability is supported
by the FW.  When passing the CQ to HW indicate that the CQ buffer has
been pre-initialized.

Doing so decreases CQ creation time.  Testing on P8 showed a single 2048
entry CQ creation time was reduced from ~395us to ~170us, which is
2.3x faster.

Signed-off-by: Daniel Jurgens 
Signed-off-by: Jack Morgenstein 
Signed-off-by: Tariq Toukan 
Signed-off-by: David S. Miller

net/mlx4_core: Use devlink region_snapshot parameter

2018-07-13T00:37:13+00:00

This parameter enables capturing region snapshot of the crspace
during critical errors. The default value of this parameter is
disabled, it can be enabled using devlink param commands.
It is possible to configure during runtime and also driver init.

Signed-off-by: Alex Vesker 
Signed-off-by: Jiri Pirko 
Reviewed-by: Moshe Shemesh 
Signed-off-by: David S. Miller

net/mlx4_core: Add Crdump FW snapshot support

2018-07-13T00:37:13+00:00

Crdump allows the driver to create a snapshot of the FW PCI
crspace and health buffer during a critical FW issue.
In case of a FW command timeout, FW getting stuck or a non zero
value on the catastrophic buffer, a snapshot will be taken.

The snapshot is exposed using devlink, cr-space, fw-health
address regions are registered on init and snapshots are attached
once a new snapshot is collected by the driver.

Signed-off-by: Alex Vesker 
Signed-off-by: Tariq Toukan 
Signed-off-by: Jiri Pirko 
Signed-off-by: David S. Miller

net/mlx4_core: Add health buffer address capability

2018-07-13T00:37:13+00:00

Health buffer address is a 32 bit PCI address offset provided by
the FW. This offset is used for reading FW health debug data
located on the shared CR space. Cr space is accessible in both
driver and FW and allows for different queries and configurations.
Health buffer size is always 64B of readable data followed by a
lock which is used to block volatile CR space access.

Signed-off-by: Alex Vesker 
Signed-off-by: Tariq Toukan 
Signed-off-by: Jiri Pirko 
Signed-off-by: David S. Miller

net/mlx4_core: Report driver version to FW

2018-05-10T20:08:25+00:00

If supported, write a driver version string to FW as part of the
INIT_HCA command.

Example of driver version: "Linux,mlx4_core,4.0-0"

Signed-off-by: Eran Ben Elisha 
Signed-off-by: Tariq Toukan 
Signed-off-by: David S. Miller