[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4d8fe881-8d36-06dd-667a-276a717a0d89@huawei.com>
Date: Fri, 10 Jan 2020 12:10:12 +0800
From: Yunsheng Lin <linyunsheng@...wei.com>
To: Jacob Keller <jacob.e.keller@...el.com>, <netdev@...r.kernel.org>
CC: <valex@...lanox.com>, <jiri@...nulli.us>
Subject: Re: [PATCH v2 0/3] devlink region trigger support
On 2020/1/10 3:33, Jacob Keller wrote:
> This series consists of patches to enable devlink to request a snapshot via
> a new DEVLINK_CMD_REGION_TRIGGER_SNAPSHOT.
>
> A reviewer might notice that the devlink health API already has such support
> for handling a similar case. However, the health API does not make sense in
> cases where the data is not related to an error condition.
Maybe we need to specify the usecases for the region trigger as suggested by
Jacob.
For example, the orginal usecase is to expose some set of flash/NVM contents.
But can it be used to dump the register of the bar space? or some binary
table in the hardware to debug some error that is not detected by hw?
>
> In this case, using the health API only for the dumping feels incorrect.
> Regions make sense when the addressable content is not captured
> automatically on error conditions, but only upon request by the devlink API.
>
> The netdevsim driver is modified to support the new trigger_snapshot
> callback as an example of how this can be used.
>
> Jacob Keller (3):
> devlink: add callback to trigger region snapshots
> devlink: introduce command to trigger region snapshot
> netdevsim: support triggering snapshot through devlink
>
> drivers/net/ethernet/mellanox/mlx4/crdump.c | 4 +-
> drivers/net/netdevsim/dev.c | 37 ++++++++++++-----
> include/net/devlink.h | 12 ++++--
> include/uapi/linux/devlink.h | 2 +
> net/core/devlink.c | 45 +++++++++++++++++++--
> 5 files changed, 80 insertions(+), 20 deletions(-)
>
Powered by blists - more mailing lists