OpenVZ / Virtuozzo kernel development (devel@openvz.org)
 help / color / mirror / Atom feed
From: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
To: khorenko@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1 v5 0/1] selftests: drv-net-hw: skip the tests that need a real interface
Date: Fri, 23 Oct 2026 22:20:09 +0300	[thread overview]
Message-ID: <20261023192121.356062-1-eva.kurchatova@virtuozzo.com> (raw)

Changes in v5:
- Follow lib.sh's order: command line, forwarding.config, then the
  driver: a NETIF_FIND_DRIVER set in forwarding.config skipped a run on
  hardware, and veths named in forwarding.config ran under
  NETIF_FIND_DRIVER.
- skip_on_veth() returns 0 when the test goes on, not 1.
- Rebased.

Link to v4: http://lore.virtuozzo.com/kernel/20261007145044.2647274-1-eva.kurchatova@virtuozzo.com/T/#t

Patchset for task https://virtuozzo.atlassian.net/browse/VSTOR-139651

Changes in v4:
- Runs that pick their interfaces by driver (NETIF_FIND_DRIVER) were
  skipped; pass them to lib.sh untouched, allowing to run now.
- Unchanged: only the first interface is judged, lib.sh builds its pair
  from that one and skips by itself when a later one is missing. Only
  a veth is detected. Everything else is configuration choice.
- Rebased.

Link to v3: http://lore.virtuozzo.com/kernel/20261006222651.2510417-1-eva.kurchatova@virtuozzo.com/T/#t
    
Changes in v3:
- Check the kind of the first interface instead of NETIF_CREATE and
  NETIF_TYPE, which stay at their defaults when forwarding.config
  names real NICs; those ran through lib.sh and were skipped here.
- Take the interfaces from the command line too, as lib.sh does.
- Rebased.

Link to v2: http://lore.virtuozzo.com/kernel/20260928194332.551992-1-eva.kurchatova@virtuozzo.com/T/#t

Changes in v2:
- Read forwarding.config before deciding, the way lib.sh does.
- One helper, skip_on_veth.sh, instead of a copy in each test.
- Add ethtool_rmon.sh, it fails on veth the same way.
- One-line comments, fix the Feature tag.
- Sent alone, 1/4 to 3/4 are merged.

Link to v1: http://lore.virtuozzo.com/kernel/20260831225137.1642608-4-eva.kurchatova@virtuozzo.com/

Eva Kurchatova (1):
  selftests: drv-net-hw: skip the tests that need a real interface

 .../testing/selftests/drivers/net/hw/Makefile |  1 +
 .../selftests/drivers/net/hw/ethtool.sh       |  5 +++
 .../drivers/net/hw/ethtool_extended_state.sh  |  5 +++
 .../selftests/drivers/net/hw/ethtool_rmon.sh  |  5 +++
 .../selftests/drivers/net/hw/hw_stats_l3.sh   |  5 +++
 .../drivers/net/hw/hw_stats_l3_gre.sh         |  5 +++
 .../selftests/drivers/net/hw/skip_on_veth.sh  | 38 +++++++++++++++++++
 7 files changed, 64 insertions(+)
 create mode 100644 tools/testing/selftests/drivers/net/hw/skip_on_veth.sh

-- 
2.56.0

_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

             reply	other threads:[~2026-10-23 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 19:20 Eva Kurchatova [this message]
2026-10-23 19:20 ` [Devel] [PATCH hci-8.1 v5 1/1] " Eva Kurchatova
2026-10-23 19:25   ` no-reply
2026-10-26 12:19     ` Eva Kurchatova (Virtuozzo)
2026-10-27 12:00 ` [Devel] [PATCH hci-8.1 v5 0/1] " Konstantin Khorenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261023192121.356062-1-eva.kurchatova@virtuozzo.com \
    --to=eva.kurchatova@virtuozzo.com \
    --cc=devel@openvz.org \
    --cc=khorenko@virtuozzo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox