diff options
author | Vladimir Oltean <vladimir.oltean@nxp.com> | 2022-12-09 20:28:17 +0300 |
---|---|---|
committer | Jakub Kicinski <kuba@kernel.org> | 2022-12-13 02:01:18 +0300 |
commit | 9e3d9ae52b5657399a7b61258cc7482434a911bb (patch) | |
tree | ebe7e882e2c8f751e6483f47df59b3484439594e /tools/perf/scripts/python/stackcollapse.py | |
parent | 8646384d80f3d3b4a66b3284dbbd8232d1b8799e (diff) | |
download | linux-9e3d9ae52b5657399a7b61258cc7482434a911bb.tar.xz |
net: dsa: mv88e6xxx: replace VTU violation prints with trace points
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@nxp.com>
Reviewed-by: Saeed Mahameed <saeed@kernel.org>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions