From: Alex Williamson <alex.williamson@redhat.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Christian König" <christian.koenig@amd.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"Michał Winiarski" <michal.winiarski@intel.com>
Subject: Re: [PATCH v2 1/1] PCI: Fix BAR resizing when VF BARs are assigned
Date: Fri, 14 Mar 2025 08:56:49 -0600 [thread overview]
Message-ID: <20250314085649.4aefc1b5.alex.williamson@redhat.com> (raw)
In-Reply-To: <20250307140349.5634-1-ilpo.jarvinen@linux.intel.com>
On Fri, 7 Mar 2025 16:03:49 +0200
Ilpo Järvinen <ilpo.jarvinen@linux.intel.com> wrote:
> __resource_resize_store() attempts to release all resources of the
> device before attempting the resize. The loop, however, only covers
> standard BARs (< PCI_STD_NUM_BARS). If a device has VF BARs that are
> assigned, pci_reassign_bridge_resources() finds the bridge window still
> has some assigned child resources and returns -NOENT which makes
> pci_resize_resource() to detect an error and abort the resize.
>
> Change the release loop to cover all resources up to VF BARs which
> allows the resize operation to release the bridge windows and attempt
> to assigned them again with the different size.
>
> As __resource_resize_store() checks first that no driver is bound to
> the PCI device before resizing is allowed, SR-IOV cannot be enabled
> during resize so it is safe to release also the IOV resources.
Is this true? pci-pf-stub doesn't teardown SR-IOV on release, which I
understand is done intentionally. Thanks,
Alex
> Fixes: 91fa127794ac ("PCI: Expose PCIe Resizable BAR support via sysfs")
> Reported-by: Michał Winiarski <michal.winiarski@intel.com>
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> ---
>
> v2:
> - Removed language about expansion ROMs
>
> drivers/pci/pci-sysfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pci/pci-sysfs.c b/drivers/pci/pci-sysfs.c
> index b46ce1a2c554..0c16751bab40 100644
> --- a/drivers/pci/pci-sysfs.c
> +++ b/drivers/pci/pci-sysfs.c
> @@ -1578,7 +1578,7 @@ static ssize_t __resource_resize_store(struct device *dev, int n,
>
> pci_remove_resource_files(pdev);
>
> - for (i = 0; i < PCI_STD_NUM_BARS; i++) {
> + for (i = 0; i < PCI_BRIDGE_RESOURCES; i++) {
> if (pci_resource_len(pdev, i) &&
> pci_resource_flags(pdev, i) == flags)
> pci_release_resource(pdev, i);
>
> base-commit: 2014c95afecee3e76ca4a56956a936e23283f05b
next prev parent reply other threads:[~2025-03-14 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 14:03 [PATCH v2 1/1] PCI: Fix BAR resizing when VF BARs are assigned Ilpo Järvinen
2025-03-14 14:56 ` Alex Williamson [this message]
2025-03-17 18:18 ` Michał Winiarski
2025-03-17 22:38 ` Alex Williamson
2025-03-18 11:42 ` Ilpo Järvinen
2025-03-18 15:01 ` Alex Williamson
2025-03-18 15:23 ` Alex Williamson
2025-03-18 12:21 ` Philipp Stanner
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=20250314085649.4aefc1b5.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=michal.winiarski@intel.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