Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Brett Creeley <bcreeley@amd.com>
To: Mohan Prasad J <mohan.prasad@microchip.com>,
	netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org
Cc: shuah@kernel.org, bryan.whitehead@microchip.com,
	UNGLinuxDriver@microchip.com, edumazet@google.com,
	pabeni@redhat.com, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, horms@kernel.org,
	brett.creeley@amd.com, rosenp@gmail.com
Subject: Re: [PATCH net-next 2/3] selftests: lan743x: Add testcase to check speed and duplex state of lan743x
Date: Wed, 4 Sep 2024 09:05:41 -0700	[thread overview]
Message-ID: <61428e08-8b88-41cf-83b6-123a857920c2@amd.com> (raw)
In-Reply-To: <20240903221549.1215842-3-mohan.prasad@microchip.com>



On 9/3/2024 3:15 PM, Mohan Prasad J wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
> 
> 
> Add testcase for checking speed and duplex states for
> lan743x network driver.
> Testcase comprises of varying the network speed and duplex
> state to 10/100/1000Mbps and half/full via ethtool.
> 
> Signed-off-by: Mohan Prasad J <mohan.prasad@microchip.com>
> ---
>   .../net/hw/microchip/lan743x/lan743x.py       | 33 +++++++++++++++++++
>   1 file changed, 33 insertions(+)
> 
> diff --git a/tools/testing/selftests/drivers/net/hw/microchip/lan743x/lan743x.py b/tools/testing/selftests/drivers/net/hw/microchip/lan743x/lan743x.py
> index f1ad97dc2..59f0be2a7 100755
> --- a/tools/testing/selftests/drivers/net/hw/microchip/lan743x/lan743x.py
> +++ b/tools/testing/selftests/drivers/net/hw/microchip/lan743x/lan743x.py
> @@ -36,12 +36,45 @@ def verify_autonegotiation(ifname: str, expected_state: str) -> None:
>       actual_state = autoneg_match.group(1)
>       ksft_eq(actual_state, expected_state)
> 
> +def set_speed_and_duplex(ifname: str, speed: str, duplex: str) -> None:
> +    """Set the speed and duplex state for the interface"""
> +    process = ethtool(f"--change {ifname} speed {speed} duplex {duplex} autoneg on")
> +
> +    if process.ret != 0:
> +        raise KsftFailEx(f"Not able to set speeed and duplex parameters for {ifname}")
> +    ksft_pr(f"Speed: {speed} Mbps, Duplex: {duplex} set for Interface: {ifname}")
> +
> +def verify_speed_and_duplex(ifname: str, expected_speed: str, expected_duplex: str) -> None:
> +    verify_link_up(ifname)
> +    """Verifying the speed and duplex state for the interface"""
> +    output = ethtool(f"{ifname}")

How does "output" get used here?

> +    with open(f"/sys/class/net/{ifname}/speed", "r") as fp:
> +        actual_speed = fp.read().strip()
> +    with open(f"/sys/class/net/{ifname}/duplex", "r") as fp:
> +        actual_duplex = fp.read().strip()

Should you check speed/duplex from both sysfs and ethtool? Maybe that's 
overkill.

Thanks,

Brett

> +
> +    ksft_eq(actual_speed, expected_speed)
> +    ksft_eq(actual_duplex, expected_duplex)
> +
>   def test_autonegotiation(cfg) -> None:
>       for state in ["off", "on"]:
>           set_autonegotiation_state(cfg.ifname, state)
>           time.sleep(5)
>           verify_autonegotiation(cfg.ifname, state)
> 
> +def test_network_speed(cfg) -> None:
> +    speeds = ["10", "100", "1000"]
> +    duplex_modes = ["half", "full"]
> +
> +    for speed in speeds:
> +        for duplex in duplex_modes:
> +            # Skip for speed = 1000Mbps, duplex = Half
> +            if speed == "1000" and duplex == "half":
> +                continue
> +            set_speed_and_duplex(cfg.ifname, speed, duplex)
> +            time.sleep(5)
> +            verify_speed_and_duplex(cfg.ifname, speed, duplex)
> + >   def main() -> None:
>       with NetDrvEpEnv(__file__) as cfg:
>           ksft_run(globs=globals(), case_pfx={"test_"}, args=(cfg,))
> --
> 2.43.0
> 

  reply	other threads:[~2024-09-04 16:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 22:15 [PATCH net-next 0/3] lan743x: This series of patches are for lan743x driver testing Mohan Prasad J
2024-09-03 22:15 ` [PATCH net-next 1/3] selftests: lan743x: Add testfile for lan743x network driver Mohan Prasad J
2024-09-04 16:10   ` Brett Creeley
2024-09-06  6:54     ` Mohan.Prasad
2024-09-03 22:15 ` [PATCH net-next 2/3] selftests: lan743x: Add testcase to check speed and duplex state of lan743x Mohan Prasad J
2024-09-04 16:05   ` Brett Creeley [this message]
2024-09-06  6:52     ` Mohan.Prasad
2024-09-03 22:15 ` [PATCH net-next 3/3] selftests: lan743x: Add testcase to check throughput " Mohan Prasad J
2024-09-04 16:15   ` Brett Creeley
2024-09-06  6:56     ` Mohan.Prasad
2024-09-04  5:30 ` [PATCH net-next 0/3] lan743x: This series of patches are for lan743x driver testing Andrew Lunn
2024-09-06  6:45   ` Mohan.Prasad
2024-09-06 12:08     ` Andrew Lunn
2024-09-09  6:42       ` Mohan.Prasad
2024-09-09 13:24         ` Andrew Lunn

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=61428e08-8b88-41cf-83b6-123a857920c2@amd.com \
    --to=bcreeley@amd.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=brett.creeley@amd.com \
    --cc=bryan.whitehead@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mohan.prasad@microchip.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rosenp@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox