On 1/20/2019 1:27 PM, Jiri Pirko wrote:
> Thu, Jan 17, 2019 at 10:59:12PM CET, era...@mellanox.com wrote:
>
> [...]
>
>> +
>> +TRACE_EVENT(devlink_health_recover_aborted,
>> +TP_PROTO(const struct devlink *devlink, const char *reporter_name,
>> + bool health_state, u64 time_sinc
Thu, Jan 17, 2019 at 10:59:12PM CET, era...@mellanox.com wrote:
[...]
>+
>+TRACE_EVENT(devlink_health_recover_aborted,
>+ TP_PROTO(const struct devlink *devlink, const char *reporter_name,
>+ bool health_state, u64 time_since_last_recover),
>+
>+ TP_ARGS(devlink, reporter_
Upon error discover, every driver can report it to the devlink health
mechanism via devlink_health_report function, using the appropriate
reporter registered to it. Driver can pass error specific context which
will be delivered to it as part of the dump / recovery callbacks.
Once an error is repor
