[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180712.173732.1019798134999587246.davem@davemloft.net>
Date: Thu, 12 Jul 2018 17:37:32 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: valex@...lanox.com
Cc: netdev@...r.kernel.org, jiri@...lanox.com, dsahern@...il.com,
andrew@...n.ch, rahul.lakkireddy@...lsio.com,
jakub.kicinski@...ronome.com
Subject: Re: [PATCH net-next v3 00/11] devlink: Add support for region
access
From: Alex Vesker <valex@...lanox.com>
Date: Thu, 12 Jul 2018 15:13:07 +0300
> This is a proposal which will allow access to driver defined address
> regions using devlink. Each device can create its supported address
> regions and register them. A device which exposes a region will allow
> access to it using devlink.
>
> The suggested implementation will allow exposing regions to the user,
> reading and dumping snapshots taken from different regions.
> 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 to be
> done.
>
> The major benefit of this support is not only to provide access to
> internal address regions which were inaccessible to the user but also
> to provide an additional way to debug complex error states using the
> region snapshots.
...
Series applied, thanks!
Powered by blists - more mailing lists