Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: David Matlack <dmatlack@google.com>
To: Josh Hilke <jrhilke@google.com>
Cc: Alex Williamson <alex@shazbot.org>,
	Vipin Sharma <vipinsh@google.com>, Shuah Khan <shuah@kernel.org>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org,
	Alex Williamson <alex.williamson@nvidia.com>
Subject: Re: [PATCH v2 08/10] selftests/vfio: igb: Factor hardware programming into igb_hw_init()
Date: Mon, 6 Jul 2026 21:16:14 +0000	[thread overview]
Message-ID: <akwbHgu5iOBlBR8k@google.com> (raw)
In-Reply-To: <20260526235417.2058313-9-jrhilke@google.com>

On 2026-05-26 11:54 PM, Josh Hilke wrote:
> From: Alex Williamson <alex.williamson@nvidia.com>
> 
> Split the device register programming out of igb_init() into a new
> igb_hw_init() helper so that the same sequence can be re-run after a
> VFIO_DEVICE_RESET to restore the registers that CTRL.RST clears.  No
> functional change for the initial path.
> 
> igb_init() now performs the one-shot setup: region size assertion, BAR
> mapping, CTRL.RST + IMC mask-all to put the device into a known state,
> and vfio_pci_msix_enable() to set up the kernel-side IRQ trigger.
> igb_hw_init() does the rest: ring pointer setup and IOVA calc,
> CTRL_EXT, PCI bus master, GCR, PHY loopback, descriptor rings, RCTL,
> TCTL, GPIE/EIAC/EIAM/EIMS/IVAR, and driver-state initialization.
> 
> vfio_pci_msix_enable() moves from after RCTL/TCTL to before all
> device-side programming.  Its only side effects are the VFIO kernel
> IRQ trigger setup and the PCI MSI-X capability bits in config space;
> neither has any ordering dependency on the 82576 device register
> writes performed in igb_hw_init().  Performing it once in igb_init()
> keeps igb_hw_init() reusable from the reset recovery path (which uses
> vfio_pci_irq_reenable() to re-arm the existing trigger).
> 
> Assisted-by: Claude:claude-opus-4-7
> Signed-off-by: Alex Williamson <alex.williamson@nvidia.com>

Reviewed-by: David Matlack <dmatlack@google.com>

  reply	other threads:[~2026-07-06 21:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26 23:54 [PATCH v2 00/10] selftests/vfio: igb: Add driver for Intel Josh Hilke
2026-05-26 23:54 ` [PATCH v2 01/10] selftests/vfio: igb: Add driver for IGB QEMU device Josh Hilke
2026-05-27  0:32   ` sashiko-bot
2026-07-06 20:30     ` David Matlack
2026-05-26 23:54 ` [PATCH v2 02/10] selftests/vfio: igb: Use PHY internal loopback on 82576 Josh Hilke
2026-05-26 23:54 ` [PATCH v2 03/10] selftests/vfio: igb: Use advanced TX and RX descriptors Josh Hilke
2026-05-27  0:14   ` sashiko-bot
2026-05-29 20:24     ` Alex Williamson
2026-05-26 23:54 ` [PATCH v2 04/10] selftests/vfio: igb: Program MSI-X interrupt routing Josh Hilke
2026-05-27  0:19   ` sashiko-bot
2026-05-29 20:24     ` Alex Williamson
2026-05-26 23:54 ` [PATCH v2 05/10] selftests/vfio: igb: Extend memcpy completion timeout for line-rate hardware Josh Hilke
2026-05-26 23:54 ` [PATCH v2 06/10] selftests/vfio: igb: Disable PCIe completion timeout retries Josh Hilke
2026-05-26 23:54 ` [PATCH v2 07/10] selftests/vfio: Add vfio_pci_irq_reenable() helper Josh Hilke
2026-07-06 21:03   ` David Matlack
2026-05-26 23:54 ` [PATCH v2 08/10] selftests/vfio: igb: Factor hardware programming into igb_hw_init() Josh Hilke
2026-07-06 21:16   ` David Matlack [this message]
2026-05-26 23:54 ` [PATCH v2 09/10] selftests/vfio: igb: Recover after DMA-read faults Josh Hilke
2026-07-06 21:16   ` David Matlack
2026-05-26 23:54 ` [PATCH v2 10/10] selftests/vfio: igb: Use offical IGB headers in selftest driver Josh Hilke
2026-05-27  2:40   ` sashiko-bot
2026-07-06 20:49   ` David Matlack
2026-07-06 20:55 ` [PATCH v2 00/10] selftests/vfio: igb: Add driver for Intel David Matlack

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=akwbHgu5iOBlBR8k@google.com \
    --to=dmatlack@google.com \
    --cc=alex.williamson@nvidia.com \
    --cc=alex@shazbot.org \
    --cc=jrhilke@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=vipinsh@google.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