[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y5OO2RgzWntMGOPg@x130>
Date: Fri, 9 Dec 2022 11:39:05 -0800
From: Saeed Mahameed <saeed@...nel.org>
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: netdev@...r.kernel.org, Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
"Hans J. Schultz" <netdev@...io-technology.com>
Subject: Re: [PATCH v2 net-next 4/4] net: dsa: mv88e6xxx: replace VTU
violation prints with trace points
On 09 Dec 19:28, Vladimir Oltean wrote:
>It is possible to trigger these VTU violation messages very easily,
>it's only necessary to send packets with an unknown VLAN ID to a port
>that belongs to a VLAN-aware bridge.
>
>Do a similar thing as for ATU violation messages, and hide them in the
>kernel's trace buffer.
>
>New usage model:
>
>$ trace-cmd list | grep mv88e6xxx
>mv88e6xxx
>mv88e6xxx:mv88e6xxx_vtu_miss_violation
>mv88e6xxx:mv88e6xxx_vtu_member_violation
>$ trace-cmd report
>
>Signed-off-by: Vladimir Oltean <vladimir.oltean@....com>
Reviewed-by: Saeed Mahameed <saeed@...nel.org>
Powered by blists - more mailing lists