[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190927081333.GF3742@nanopsycho>
Date: Fri, 27 Sep 2019 10:13:33 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Yunsheng Lin <linyunsheng@...wei.com>
Cc: jiri@...lanox.com, valex@...lanox.com, davem@...emloft.net,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linuxarm@...wei.com" <linuxarm@...wei.com>
Subject: Re: [question] About triggering a region snapshot through the
devlink cmd
Fri, Sep 27, 2019 at 09:40:47AM CEST, linyunsheng@...wei.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".
>
Powered by blists - more mailing lists