[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <dd4b73d7-0219-9db5-4d8e-4150cfa8fbda@gmail.com>
Date: Thu, 19 Jul 2018 10:21:20 -0600
From: David Ahern <dsahern@...il.com>
To: Alex Vesker <valex@...lanox.com>, netdev@...r.kernel.org,
jiri@...lanox.com
Subject: Re: [PATCH iproute2 net-next] devlink: Add support for devlink-region
access
On 7/17/18 2:34 AM, Alex Vesker wrote:
> Devlink region allows access to driver defined address regions.
> Each device can create its supported address regions and register
> them. A device which exposes a region will allow access to it
> using devlink.
>
> This support allows reading and dumping regions snapshots as well
> as presenting information such as region size and current available
> snapshots.
>
> A snapshot represents a memory image of a region taken by the driver.
> If a device collects a snapshot of an address region it can be later
> exposed using devlink region read or dump commands.
> This functionality allows for future analyses on the snapshots.
>
> The dump command is designed to read the full address space of a
> region or of a snapshot unlike the read command which allows
> reading only a specific section in a region/snapshot indicated by
> an address and a length, current support is for reading and dumping
> for a previously taken snapshot ID.
>
> New commands added:
> devlink region show [ DEV/REGION ]
> devlink region delete DEV/REGION snapshot SNAPSHOT_ID
> devlink region dump DEV/REGION [ snapshot SNAPSHOT_ID ]
> devlink region read DEV/REGION [ snapshot SNAPSHOT_ID ]
> address ADDRESS length length
>
> Signed-off-by: Alex Vesker <valex@...lanox.com>
> Signed-off-by: Jiri Pirko <jiri@...lanox.com>
> ---
> devlink/devlink.c | 485 +++++++++++++++++++++++++++++++++++++++++++++-
> man/man8/devlink-region.8 | 131 +++++++++++++
> man/man8/devlink.8 | 1 +
> 3 files changed, 616 insertions(+), 1 deletion(-)
> create mode 100644 man/man8/devlink-region.8
>
applied to iproute2-next. Thanks
Powered by blists - more mailing lists