net/mlx5: FW tracer, events handling
The tracer has one event, event 0x26, with two subtypes: - Subtype 0: Ownership change - Subtype 1: Traces available An ownership change occurs in the following cases: 1- Owner releases his ownership, in this case, an event will be sent to inform others to reattempt acquire ownership. 2- Ownership was taken by a higher priority tool, in this case the owner should understand that it lost ownership, and go through tear down flow. The second subtype indicates that there are traces in the trace buffer, in this case, the driver polls the tracer buffer for new traces, parse them and prepares the messages for printing. The HW starts tracing from the first address in the tracer buffer. Driver receives an event notifying that new trace block exists. HW posts a timestamp event at the last 8B of every 256B block. Comparing the timestamp to the last handled timestamp would indicate that this is a new trace block. Once the new timestamp is detected, the entire block is considered valid. Block validation and parsing, should be done after copying the current block to a different location, in order to avoid block overwritten during processing. Signed-off-by:Feras Daoud <ferasda@mellanox.com> Signed-off-by:
Saeed Mahameed <saeedm@mellanox.com>
parent
e9cad2ce
-
mentioned in commit 6e188646
-
mentioned in commit 11e249ce
-
mentioned in commit e114f15d
-
mentioned in commit 29a5af91
-
mentioned in commit 48e79555
-
mentioned in commit 9e19f93f
-
mentioned in commit 652418d8
-
mentioned in commit 0e92af67
-
mentioned in commit 8a6740fd
-
mentioned in commit accd5d55
-
mentioned in commit d7aeb591
-
mentioned in commit 94c8485b
-
mentioned in commit e8ba688a
-
mentioned in commit da2396b5
-
mentioned in commit 8a100f6e
-
mentioned in commit d07ef3a8
Please register or sign in to comment