From: Jiri Pirko <jiri@resnulli.us>
To: Yunsheng Lin <linyunsheng@huawei.com>
Cc: jiri@mellanox.com, valex@mellanox.com, davem@davemloft.net,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linuxarm@huawei.com" <linuxarm@huawei.com>
Subject: Re: [question] About triggering a region snapshot through the devlink cmd
Date: Fri, 27 Sep 2019 10:13:33 +0200 [thread overview]
Message-ID: <20190927081333.GF3742@nanopsycho> (raw)
In-Reply-To: <f1436c35-e8be-7b9d-c2f5-b6403348f87a@huawei.com>
Fri, Sep 27, 2019 at 09:40:47AM CEST, linyunsheng@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".
>
next prev parent reply other threads:[~2019-09-27 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 7:40 [question] About triggering a region snapshot through the devlink cmd Yunsheng Lin
2019-09-27 8:13 ` Jiri Pirko [this message]
2019-09-29 12:21 ` Yunsheng Lin
-- strict thread matches above, loose matches on Subject: below --
2020-01-07 17:33 Keller, Jacob E
[not found] ` <HE1PR0502MB3771BD83B728249E6C21967AC33E0@HE1PR0502MB3771.eurprd05.prod.outlook.com>
[not found] ` <HE1PR0502MB3771D512C2D23F551EB922F4C33E0@HE1PR0502MB3771.eurprd05.prod.outlook.com>
2020-01-08 19:14 ` FW: " Jacob Keller
2020-01-09 19:41 ` Jakub Kicinski
2020-01-09 20:05 ` Jacob Keller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190927081333.GF3742@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=linuxarm@huawei.com \
--cc=linyunsheng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=valex@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).