Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 11 12月, 2018 6 次提交
  3. 10 12月, 2018 1 次提交
  5. 07 12月, 2018 1 次提交
  7. 04 12月, 2018 5 次提交
  9. 30 11月, 2018 6 次提交
  11. 27 11月, 2018 6 次提交
    • S
      net/mlx5: Device events, Use async events chain · 69c1280b
      由 Saeed Mahameed 提交于 
      Move all the generic async events handling into new specific events
handling file events.c to keep eq.c file clean from concrete event logic
handling.

Use new API to register for NOTIFY_ANY to handle generic events and
dispatch allowed events to mlx5_core consumers (mlx5_ib and mlx5e)
Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      69c1280b
    • S
      net/mlx5: Resource tables, Use async events chain · 221c14f3
      由 Saeed Mahameed 提交于 
      Remove the explicit call to QP/SRQ resources events handlers on several FW
events and let resources logic register resources events notifiers via the
new API.
Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      221c14f3
    • S
      net/mlx5: CmdIF, Use async events chain · 71edc69c
      由 Saeed Mahameed 提交于 
      Remove the explicit call to mlx5_cmd_comp_handler on MLX5_EVENT_TYPE_CMD
and let command interface to register its own handler when its ready.
Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      71edc69c
    • S
      net/mlx5: FWPage, Use async events chain · 0cf53c12
      由 Saeed Mahameed 提交于 
      Remove the explicit call to mlx5_core_req_pages_handler on
MLX5_EVENT_TYPE_PAGE_REQUEST and let FW page logic  to register its own
handler when its ready.
Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      0cf53c12
    • S
      net/mlx5: Clock, Use async events chain · 41069256
      由 Saeed Mahameed 提交于 
      Remove the explicit call to mlx5_pps_event on MLX5_EVENT_TYPE_PPS_EVENT
and let clock logic to register its own handler when its ready.
Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      41069256
    • S
      net/mlx5: EQ, Introduce atomic notifier chain subscription API · 0f597ed4
      由 Saeed Mahameed 提交于 
      Use atomic_notifier_chain to fire firmware events at internal mlx5 core
components such as eswitch/fpga/clock/FW tracer/etc.., this is to
avoid explicit calls from low level mlx5_core to upper components and to
simplify the mlx5_core API for future developments.

Simply provide register/unregister notifiers API and call the notifier
chain on firmware async events.

Example: to subscribe to a FW event:
struct mlx5_nb port_event;

MLX5_NB_INIT(&port_event, port_event_handler, PORT_CHANGE);
mlx5_eq_notifier_register(mdev, &port_event);

where:
 - port_event_handler is the notifier block callback.
 - PORT_EVENT is the suffix of MLX5_EVENT_TYPE_PORT_CHANGE.

The above will guarantee that port_event_handler will receive all FW
events of the type MLX5_EVENT_TYPE_PORT_CHANGE.

To receive all FW/HW events one can subscribe to
MLX5_EVENT_TYPE_NOTIFY_ANY.

The next few patches will start moving all mlx5 core components to use
this new API and cleanup mlx5_eq_async_int misx handler from component
explicit calls and specific logic.
Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      0f597ed4
  13. 21 11月, 2018 9 次提交
  15. 13 11月, 2018 2 次提交
  17. 09 11月, 2018 1 次提交
  19. 07 11月, 2018 1 次提交
  21. 19 10月, 2018 2 次提交