From: sashiko-bot@kernel.org
To: "Josh Hilke" <jrhilke@google.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v3 2/9] vfio: selftests: igb: Use PHY internal loopback on 82576
Date: Wed, 08 Jul 2026 23:28:07 +0000 [thread overview]
Message-ID: <20260708232808.184BD1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260708-igb_v3_b4-v3-2-1272650ca614@google.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit message incorrectly references removing and keeping macros and code that do not exist in the baseline or the patch diff.
--
--- Patch [2]: [PATCH v3 2/9] vfio: selftests: igb: Use PHY internal loopback on 82576 ---
commit 2d54b65042a5cbe6702c330df52d94e7c2ff3b57
Author: Alex Williamson <alex.williamson@nvidia.com>
vfio: selftests: igb: Use PHY internal loopback on 82576
This commit replaces igb_phy_setup_autoneg() with igb_setup_loopback() to use
PHY internal loopback on the 82576 device instead of MAC loopback, aligning
with the datasheet requirements for real hardware. It forces the MAC into 1Gb/s
full duplex with link up to ensure the descriptor engine runs. The patch also
maintains compatibility with QEMU's emulated igb behavior without needing
environment-specific code paths.
> The submitted driver also wrote bit 14 (link disable) to PHY register
> 16 (port control). Datasheet 3.5.6.3.1 describes this as required for
> 10/100Mb/s but explicitly "not a must for 1G", and the kernel ethtool
> selftest omits it. It is dropped here. Flagging the removal in case a
> future regression bisects to this commit.
>
> Remove igb_read_phy() and the PHY status macros it served, which become
> unused: IGB_PHY_STATUS_REG_OFFSET, IGB_PHY_STATUS_AN_COMP. Keep
> IGB_PHY_CTRL_AN_ENABLE and IGB_PHY_CTRL_AN_RESTART for the QEMU-only
> autoneg kick; add the PHY ctrl loopback and CTRL force-link macros.
[Severity: Medium]
This isn't a bug in the code, but the commit message references removing and
keeping macros and code that do not exist in the baseline or the patch diff.
Looking at the baseline code being modified, igb_phy_setup_autoneg() did not
write to PHY register 16. It also used standard macros like MII_BMCR and
BMSR_ANEGCOMPLETE rather than IGB_PHY_STATUS_REG_OFFSET,
IGB_PHY_STATUS_AN_COMP, or IGB_PHY_CTRL_AN_ENABLE.
Could this part of the commit message be a leftover from an earlier version
of the patch series?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260708-igb_v3_b4-v3-0-1272650ca614@google.com?part=2
next prev parent reply other threads:[~2026-07-08 23:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 23:18 [PATCH v3 0/9] vfio: selftests: Add driver for Intel Ethernet Gigabit Controller (IGB) Josh Hilke
2026-07-08 23:18 ` [PATCH v3 1/9] vfio: selftests: igb: Add driver for IGB QEMU device Josh Hilke
2026-07-08 23:31 ` sashiko-bot
2026-07-09 19:23 ` Josh Hilke
2026-07-08 23:18 ` [PATCH v3 2/9] vfio: selftests: igb: Use PHY internal loopback on 82576 Josh Hilke
2026-07-08 23:28 ` sashiko-bot [this message]
2026-07-09 19:27 ` Josh Hilke
2026-07-08 23:18 ` [PATCH v3 3/9] vfio: selftests: igb: Use advanced TX and RX descriptors Josh Hilke
2026-07-08 23:29 ` sashiko-bot
2026-07-09 20:43 ` Josh Hilke
2026-07-09 21:33 ` Alex Williamson
2026-07-08 23:18 ` [PATCH v3 4/9] vfio: selftests: igb: Program MSI-X interrupt routing Josh Hilke
2026-07-08 23:33 ` sashiko-bot
2026-07-09 20:44 ` Josh Hilke
2026-07-09 22:59 ` Alex Williamson
2026-07-08 23:18 ` [PATCH v3 5/9] vfio: selftests: igb: Extend memcpy completion timeout for line-rate hardware Josh Hilke
2026-07-08 23:18 ` [PATCH v3 6/9] vfio: selftests: igb: Disable PCIe completion timeout retries Josh Hilke
2026-07-08 23:31 ` sashiko-bot
2026-07-09 22:48 ` Josh Hilke
2026-07-09 22:59 ` Alex Williamson
2026-07-08 23:18 ` [PATCH v3 7/9] vfio: selftests: Add helpers to re-enable interrupts Josh Hilke
2026-07-08 23:18 ` [PATCH v3 8/9] vfio: selftests: igb: Factor hardware programming into igb_hw_init() Josh Hilke
2026-07-08 23:18 ` [PATCH v3 9/9] vfio: selftests: igb: Recover after DMA-read faults Josh Hilke
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=20260708232808.184BD1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=jrhilke@google.com \
--cc=kvm@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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