[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZzZbqll+zj8o+Umc@shell.armlinux.org.uk>
Date: Thu, 14 Nov 2024 20:20:58 +0000
From: "Russell King (Oracle)" <linux@...linux.org.uk>
To: Kory Maincent <kory.maincent@...tlin.com>
Cc: Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org
Subject: Re: Testing selectable timestamping - where are the tools for this
feature?
On Wed, Nov 13, 2024 at 03:57:56PM +0000, Russell King (Oracle) wrote:
> On Wed, Nov 13, 2024 at 04:16:02PM +0100, Kory Maincent wrote:
> > You simply need to install python python-yaml and maybe others python
> > subpackages.
> > Copy the tool "tools/net/ynl" and the specs "Documentation/netlink/" on the
> > board.
> >
> > Then run the ynl commands.
>
> Thanks... fairly unweildly but at least it's functional. However,
> running the first, I immediately find a problem:
>
> # ./ynl/cli.py --spec netlink/specs/ethtool.yaml --no-schema --dump tsinfo-get --json '{"header":{"dev-name":"eth0"}}'
>
> One would expect this to only return results for eth0 ? I get:
Here's the nlmon packet capture for the ynl request:
0x0000: 0004 0338 0000 0000 0000 0000 0000 0010 ...8............
0x0010: 2400 0000 1500 0503 f9d3 0000 0000 0000 $...............
0x0020: 1901 0000 1000 0180 0900 0200 6574 6832 ............eth2
0x0030: 0000 0000 ....
Length: 0x00000024
Family ID: 0x0015 (ethtool)
Flags: 0x0305 (Return all matching, Specify tree root, ack, request)
Sequence: 0x0000d3f9
Port ID: 0x00000000
Command: 0x19
Family Version: 0x01
Then 16 bytes of data that does contain the interface name given to
YNL. I haven't parsed that, it seems to require manual effort to do
so as wireshark is unable to do so.
I'd be guessing to draw any conclusions from this without deeper
analysis.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
Powered by blists - more mailing lists