From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, aaronlewis@google.com, bhelgaas@google.com,
dmatlack@google.com, vipinsh@google.com, seanjc@google.com,
jrhilke@google.com, kevin.tian@intel.com
Subject: Re: [PATCH] vfio/pci: Separate SR-IOV VF dev_set
Date: Wed, 2 Jul 2025 13:00:31 -0300 [thread overview]
Message-ID: <20250702160031.GB1139770@nvidia.com> (raw)
In-Reply-To: <20250626225623.1180952-1-alex.williamson@redhat.com>
On Thu, Jun 26, 2025 at 04:56:18PM -0600, Alex Williamson wrote:
> @@ -2149,7 +2149,7 @@ int vfio_pci_core_register_device(struct vfio_pci_core_device *vdev)
> return -EBUSY;
> }
>
> - if (pci_is_root_bus(pdev->bus)) {
> + if (pci_is_root_bus(pdev->bus) || pdev->is_virtfn) {
> ret = vfio_assign_device_set(&vdev->vdev, vdev);
> } else if (!pci_probe_reset_slot(pdev->slot)) {
> ret = vfio_assign_device_set(&vdev->vdev, pdev->slot);
What about the logic in vfio_pci_dev_set_resettable()?
I guess in most cases vfio_pci_dev_set_resettable() == NULL already
for VFs since it would be rare that the PFs and VFs are all under
VFIO.
But it could happen and this would permanently block hot reset? Maybe
just mention it in the commit?
I guess the commit message is also trying to say that we don't use
VFIO_DEVICE_PCI_HOT_RESET if VFs are present on either the VF or
PF - and this change will block that.
All VF resets should go through VFIO_DEVICE_RESETF. If you want to
slot/bus reset the PF then you have to disable SRIOV first.
?
Jason
next prev parent reply other threads:[~2025-07-02 16:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 22:56 [PATCH] vfio/pci: Separate SR-IOV VF dev_set Alex Williamson
2025-06-30 6:32 ` Tian, Kevin
2025-06-30 13:15 ` Yi Liu
2025-06-30 14:57 ` Alex Williamson
2025-07-02 16:00 ` Jason Gunthorpe [this message]
2025-07-02 17:50 ` Alex Williamson
2025-07-02 17:55 ` Jason Gunthorpe
2025-07-03 6:10 ` Tian, Kevin
2025-07-03 13:23 ` Jason Gunthorpe
2025-07-03 20:29 ` Alex Williamson
2025-07-03 23:35 ` Jason Gunthorpe
2025-07-15 18:42 ` Alex Williamson
2025-07-15 18:53 ` Jason Gunthorpe
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=20250702160031.GB1139770@nvidia.com \
--to=jgg@nvidia.com \
--cc=aaronlewis@google.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=dmatlack@google.com \
--cc=jrhilke@google.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=seanjc@google.com \
--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 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.