The Linux Kernel
4.18.0-553.58.1.el8_10.x86_64
  • Linux kernel licensing rules
  • The Linux kernel user’s and administrator’s guide
  • The Linux kernel user-space API guide
  • Working with the kernel development community
  • Development tools for the kernel
  • How to write kernel documentation
  • Kernel Hacking Guides
  • Linux Tracing Technologies
  • Kernel Maintainer Handbook
  • The Linux driver implementer’s API guide
  • Core API Documentation
  • InfiniBand
  • Linux Media Subsystem Documentation
  • Linux Networking Documentation
  • The Linux Input Documentation
  • Linux GPU Driver Developer’s Guide
  • Security Documentation
  • Linux Sound Subsystem Documentation
  • Linux Kernel Crypto API
  • Linux Filesystems API
  • Linux Memory Management Documentation
  • BPF Documentation
  • Linux PCI Bus Subsystem
  • Assembler Annotations
  • SuperH Interfaces Guide
  • x86 architecture specifics
  • Korean translations
  • Chinese translations
  • Japanese translations
The Linux Kernel
  • Docs »
  • mlx4 devlink support
  • View page source

mlx4 devlink support¶

This document describes the devlink features implemented by the mlx4 device driver.

Parameters¶

Generic parameters implemented¶
Name Mode
internal_err_reset driverinit, runtime
max_macs driverinit
region_snapshot_enable driverinit, runtime

The mlx4 driver also implements the following driver-specific parameters.

Driver-specific parameters implemented¶
Name Type Mode Description
enable_64b_cqe_eqe Boolean driverinit Enable 64 byte CQEs/EQEs, if the FW supports it.
enable_4k_uar Boolean driverinit Enable using the 4k UAR.

The mlx4 driver supports reloading via DEVLINK_CMD_RELOAD

Regions¶

The mlx4 driver supports dumping the firmware PCI crspace and health buffer during a critical firmware issue.

In case a firmware command times out, firmware getting stuck, or a non zero value on the catastrophic buffer, a snapshot will be taken by the driver.

The cr-space region will contain the firmware PCI crspace contents. The fw-health region will contain the device firmware’s health buffer. Snapshots for both of these regions are taken on the same event triggers.


© Copyright The kernel development community.

Built with Sphinx using a theme provided by Read the Docs.