On Fri, Aug 02, 2019 at 03:34:54PM -0400, Vivien Didelot wrote: > Usually kernel drivers set the regs->len value to the same length as > info->regdump_len, which was used for the allocation. In case where > regs->len is smaller than the allocated info->regdump_len length, > we may assume that the dump contains a nested set of registers. > > This becomes handy for kernel drivers to expose registers of an > underlying network conduit unfortunately not exposed to userspace, > as found in network switching equipment for example. > > This patch adds support for recursing into the dump operation if there > is enough room for a nested ethtool_drvinfo structure containing a > valid driver name, followed by a ethtool_regs structure like this: > > 0 regs->len info->regdump_len > v v v > +--------------+-----------------+--------------+-- - --+ > | ethtool_regs | ethtool_drvinfo | ethtool_regs | | > +--------------+-----------------+--------------+-- - --+ > > Signed-off-by: Vivien Didelot <vivien.dide...@gmail.com>
I wasn't sure what to do with this one, given the disucssion that followed. But since Dave merged "net: dsa: dump CPU port regs through master" for net-next, I went ahead and queued this one for the next release. If that was the wrong thing to do, speak-up now! Thanks, John -- John W. Linville Someday the world will need a hero, and you linvi...@tuxdriver.com might be all we have. Be ready.
