All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Machata <petrm@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>,
	<edumazet@google.com>, <pabeni@redhat.com>,
	<andrew+netdev@lunn.ch>, <horms@kernel.org>,
	<danieller@nvidia.com>, <petrm@nvidia.com>, <shuah@kernel.org>,
	<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH net-next] selftests: drv-net: hide the devlink port_split test
Date: Mon, 10 Aug 2026 13:04:48 +0200	[thread overview]
Message-ID: <87jypy9qy7.fsf@pmachata.org> (raw)
In-Reply-To: <20260808164843.2475226-1-kuba@kernel.org> (Jakub Kicinski's message of "Sat, 8 Aug 2026 09:48:43 -0700")

Jakub Kicinski <kuba@kernel.org> writes:

> The devlink port_split test has limited applicability.
> NICs (as opposed to switches) require at least a re-probe
> to apply the split configuration.

Interesting, apparently some NICs require reboot after devlink port
split. Hmm, should I just move the test to drivers/mlxsw?

> On top of that the test is not compatible with our driver env,
> it just splits all ports on the system, not only what NETIF
> points at.
>
> Long term we may want to add some indication in devlink whether
> the port splitting is runtime (cmode of sorts), and fix the
> test to follow driver env. But since no (known) NIC driver can
> support runtime anyway let's just hide the test from the selftest
> framework by moving it to extra files.

Sure, go for it.

> Having this test randomly break unrelated NICs within the DUT
> makes people implement allow-lists for ksft, which then means
> their setups don't run new tests.

So I'm fine with the patch, but I don't buy this argument. People
presumably understand that allow-listing implies that only the, well,
allowed tests will be run. Presumably there was a history of new stuff
blowing up, or gradual enablement or whatever, otherwise why not just
blacklist the one problematic one? I.e. don't blame the existence of
allow-lists on devlink_port_split.

> Signed-off-by: Jakub Kicinski <kuba@kernel.org>

Reviewed-by: Petr Machata <petrm@nvidia.com>

> ---
> CC: danieller@nvidia.com
> CC: petrm@nvidia.com
> CC: shuah@kernel.org
> CC: linux-kselftest@vger.kernel.org
> ---
>  tools/testing/selftests/drivers/net/hw/Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/drivers/net/hw/Makefile b/tools/testing/selftests/drivers/net/hw/Makefile
> index 234db5c2c90c..ab13f58d703e 100644
> --- a/tools/testing/selftests/drivers/net/hw/Makefile
> +++ b/tools/testing/selftests/drivers/net/hw/Makefile
> @@ -19,7 +19,6 @@ TEST_GEN_FILES := \
>  
>  TEST_PROGS = \
>  	csum.py \
> -	devlink_port_split.py \
>  	devlink_rate_cross_esw.py \
>  	devlink_rate_tc_bw.py \
>  	devmem.py \
> @@ -55,6 +54,7 @@ TEST_PROGS = \
>  	#
>  
>  TEST_FILES := \
> +	devlink_port_split.py \
>  	devmem_lib.py \
>  	ethtool_lib.sh \
>  	#

  reply	other threads:[~2026-08-10 11:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-08 16:48 [PATCH net-next] selftests: drv-net: hide the devlink port_split test Jakub Kicinski
2026-08-10 11:04 ` Petr Machata [this message]
2026-08-10 18:13   ` Jakub Kicinski

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=87jypy9qy7.fsf@pmachata.org \
    --to=petrm@nvidia.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=danieller@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.