On 2019/9/27 16:13, Jiri Pirko wrote: > Fri, Sep 27, 2019 at 09:40:47AM CEST, linyunsh...@huawei.com wrote: >> Hi, Jiri & Alex >> >> It seems that a region' snapshot is only created through the >> driver when some error is detected, for example: >> mlx4_crdump_collect_fw_health() -> devlink_region_snapshot_create() >> >> We want to trigger a region' snapshot creation through devlink >> cmd, maybe by adding the "devlink region triger", because we want >> to check some hardware register/state when the driver or the hardware >> does not detect the error sometimes. >> >> Does about "devlink region triger" make sense? >> >> If yes, is there plan to implement it? or any suggestion to implement >> it? > > Actually, the plan is co convert mlx4 to "devlink health" api. Mlx5 > already uses that. > > You should look into "devlink health".
Thanks for mentioning the "devlink health" api. I has sent a RFC adding the support of the dump hardware mac table. Please have a look, any comment or suggestion will be very helpful. > >> > >
