From: Jakub Kicinski <kuba@kernel.org>
To: Maciek Machnikowski <maciek@machnikowski.net>
Cc: netdev@vger.kernel.org, richardcochran@gmail.com,
milena.olech@intel.com, willemdebruijn.kernel@gmail.com,
andrew@lunn.ch, vadim.fedorenko@linux.dev, horms@kernel.org
Subject: Re: [PATCH v6 net-next 3/3] selftests:net: Implement ptp4l sync test using netdevsim
Date: Mon, 18 May 2026 17:42:09 -0700 [thread overview]
Message-ID: <20260518174209.41e2e039@kernel.org> (raw)
In-Reply-To: <20260513094520.325693-4-maciek@machnikowski.net>
On Wed, 13 May 2026 11:45:20 +0200 Maciek Machnikowski wrote:
> Add PTP synchronization test using ptp4l and netdevsim.
>
> The test creates two netdevsim adapters, links them together
> and runs the ptp4l leader and ptp4l follower on two ends
> of the netdevsim link and waits for the follower to report the
> synchronized state (s2) in its output log.
>
> This implementation runs the test runs over IPv4 link.
> @@ -135,3 +135,4 @@ CONFIG_VLAN_8021Q=y
> CONFIG_VXLAN=m
> CONFIG_XFRM_INTERFACE=m
> CONFIG_XFRM_USER=m
> +CONFIG_PTP_1588_CLOCK_MOCK=y
config needs to be sorted too
> diff --git a/tools/testing/selftests/net/ptp.py b/tools/testing/selftests/net/ptp.py
> new file mode 100755
> index 000000000000..dd6f12cf3d91
> --- /dev/null
> +++ b/tools/testing/selftests/net/ptp.py
> @@ -0,0 +1,184 @@
> +#!/usr/bin/env python3
> +# SPDX-License-Identifier: GPL-2.0-only
> +#
> +# By Maciek Machnikowski <maciek@machnikowski.net> (c) 2026,
> +#
> +# Self-tests for HW timestamping and 1588 synchronization
> +#
> +# This test runs a ptp4l leader/follower pair and waits for follower sync
> +# state (s2), using one common execution path.
> +#
> +# By default, it:
> +# - Creates two netdevsim instances in separate namespaces
> +# - Assigns IPv4 addresses and links them together
> +# - Uses those interfaces as leader/follower endpoints for ptp4l
> +# Optional: --leader and --follower override endpoints with existing
> +# interfaces. Each argument can be either "ifname" (initial netns) or
> +# "netns:ifname". Both options must be provided together.
Please use the existing DrvEpEnv infra!?
> +import os
> +import shutil
> +import subprocess
And existing helpers from net/lib/py
There's a bunch of legit-looking pylint warnings, too.
The expectation is that the warnings levels higher than R should be
addressed, but the Rs here also seem legit
prev parent reply other threads:[~2026-05-19 0:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 9:45 [PATCH v6 net-next 0/3] Implement PTP support in netdevsim Maciek Machnikowski
2026-05-13 9:45 ` [PATCH v6 net-next 1/3] ptp_mock: Expose ptp_clock_info to external drivers Maciek Machnikowski
2026-05-13 9:45 ` [PATCH v6 net-next 2/3] netdevsim: Implement basic ptp support Maciek Machnikowski
2026-05-17 14:07 ` Simon Horman
2026-05-13 9:45 ` [PATCH v6 net-next 3/3] selftests:net: Implement ptp4l sync test using netdevsim Maciek Machnikowski
2026-05-19 0:42 ` Jakub Kicinski [this message]
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=20260518174209.41e2e039@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=horms@kernel.org \
--cc=maciek@machnikowski.net \
--cc=milena.olech@intel.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=vadim.fedorenko@linux.dev \
--cc=willemdebruijn.kernel@gmail.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