Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	linux-pci@vger.kernel.org, "Bjorn Helgaas" <bhelgaas@google.com>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Michał Winiarski" <michal.winiarski@intel.com>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	amd-gfx@lists.freedesktop.org, "David Airlie" <airlied@gmail.com>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Lucas De Marchi" <lucas.demarchi@intel.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Tvrtko Ursulin" <tursulin@ursulin.net>,
	?UTF-8?q?Thomas=20Hellstr=C3=B6m?=
	<thomas.hellstrom@linux.intel.com>,
	linux-kernel@vger.kernel.org
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH 05/11] PCI: Add pci_rebar_size_supported() helper
Date: Thu, 11 Sep 2025 10:27:14 +0200	[thread overview]
Message-ID: <75167aa2-d974-44ec-9aa5-1a18acdfc091@amd.com> (raw)
In-Reply-To: <20250911075605.5277-6-ilpo.jarvinen@linux.intel.com>



On 11.09.25 09:55, Ilpo Järvinen wrote:
> Many callers of pci_rebar_get_possible_sizes() are interested in
> finding out if a particular BAR Size (PCIe r6.2 sec. 7.8.6.3) is
> supported by the particular BAR.
> 
> Add pci_rebar_size_supported() into PCI core to make it easy for the
> drivers to determine if the BAR Size is supported or not.
> 
> Use the new function in pci_resize_resource() and in
> pci_iov_vf_bar_set_size().
> 
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> ---
>  drivers/pci/iov.c   |  7 +------
>  drivers/pci/rebar.c | 29 +++++++++++++++++++++++------
>  include/linux/pci.h |  1 +
>  3 files changed, 25 insertions(+), 12 deletions(-)
> 
> diff --git a/drivers/pci/iov.c b/drivers/pci/iov.c
> index ac4375954c94..51844a9176a0 100644
> --- a/drivers/pci/iov.c
> +++ b/drivers/pci/iov.c
> @@ -1334,7 +1334,6 @@ EXPORT_SYMBOL_GPL(pci_sriov_configure_simple);
>   */
>  int pci_iov_vf_bar_set_size(struct pci_dev *dev, int resno, int size)
>  {
> -	u32 sizes;
>  	int ret;
>  
>  	if (!pci_resource_is_iov(resno))
> @@ -1343,11 +1342,7 @@ int pci_iov_vf_bar_set_size(struct pci_dev *dev, int resno, int size)
>  	if (pci_iov_is_memory_decoding_enabled(dev))
>  		return -EBUSY;
>  
> -	sizes = pci_rebar_get_possible_sizes(dev, resno);
> -	if (!sizes)
> -		return -ENOTSUPP;
> -
> -	if (!(sizes & BIT(size)))
> +	if (!pci_rebar_size_supported(dev, resno, size))
>  		return -EINVAL;
>  
>  	ret = pci_rebar_set_size(dev, resno, size);
> diff --git a/drivers/pci/rebar.c b/drivers/pci/rebar.c
> index 64315dd8b6bb..735d9afd6ab1 100644
> --- a/drivers/pci/rebar.c
> +++ b/drivers/pci/rebar.c
> @@ -3,6 +3,7 @@
>   * PCI Resizable BAR Extended Capability handling.
>   */
>  
> +#include <linux/bits.h>
>  #include <linux/bitfield.h>
>  #include <linux/errno.h>
>  #include <linux/export.h>
> @@ -124,6 +125,27 @@ u32 pci_rebar_get_possible_sizes(struct pci_dev *pdev, int bar)
>  }
>  EXPORT_SYMBOL(pci_rebar_get_possible_sizes);
>  
> +/**
> + * pci_rebar_size_supported - check if size is supported for BAR
> + * @pdev: PCI device
> + * @bar: BAR to check
> + * @size: size as defined in the PCIe spec (0=1MB, 31=128TB)
> + *
> + * Return: %true if @bar is resizable and @size is a supported, otherwise
> + *	   %false.
> + */
> +bool pci_rebar_size_supported(struct pci_dev *pdev, int bar, int size)
> +{
> +	u64 sizes;
> +
> +	sizes = pci_rebar_get_possible_sizes(pdev, bar);

> +	if (!sizes)
> +		return false;
> +
> +	return BIT(size) & sizes;

Checking size for zero first looks superfluous.

Regards,
Christian.

> +}
> +EXPORT_SYMBOL_GPL(pci_rebar_size_supported);
> +
>  /**
>   * pci_rebar_get_current_size - get the current size of a Resizable BAR
>   * @pdev: PCI device
> @@ -231,7 +253,6 @@ int pci_resize_resource(struct pci_dev *dev, int resno, int size)
>  	struct resource *res = pci_resource_n(dev, resno);
>  	struct pci_host_bridge *host;
>  	int old, ret;
> -	u32 sizes;
>  
>  	/* Check if we must preserve the firmware's resource assignment */
>  	host = pci_find_host_bridge(dev->bus);
> @@ -245,11 +266,7 @@ int pci_resize_resource(struct pci_dev *dev, int resno, int size)
>  	if (pci_resize_is_memory_decoding_enabled(dev, resno))
>  		return -EBUSY;
>  
> -	sizes = pci_rebar_get_possible_sizes(dev, resno);
> -	if (!sizes)
> -		return -ENOTSUPP;
> -
> -	if (!(sizes & BIT(size)))
> +	if (!pci_rebar_size_supported(dev, resno, size))
>  		return -EINVAL;
>  
>  	old = pci_rebar_get_current_size(dev, resno);
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index 6f0c31290675..917c3b897739 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -1423,6 +1423,7 @@ void pci_release_resource(struct pci_dev *dev, int resno);
>  int pci_rebar_bytes_to_size(u64 bytes);
>  resource_size_t pci_rebar_size_to_bytes(int size);
>  u32 pci_rebar_get_possible_sizes(struct pci_dev *pdev, int bar);
> +bool pci_rebar_size_supported(struct pci_dev *pdev, int bar, int size);
>  int __must_check pci_resize_resource(struct pci_dev *dev, int i, int size);
>  
>  int pci_select_bars(struct pci_dev *dev, unsigned long flags);


  reply	other threads:[~2025-09-11  8:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-11  7:55 [PATCH 00/11] PCI: Resizable BAR improvements Ilpo Järvinen
2025-09-11  7:55 ` [PATCH 01/11] PCI: Move Resizable BAR code into rebar.c Ilpo Järvinen
2025-09-11  7:55 ` [PATCH 02/11] PCI: Cleanup pci_rebar_bytes_to_size() and move " Ilpo Järvinen
2025-09-11 17:25   ` Ruhl, Michael J
2025-09-11  7:55 ` [PATCH 03/11] PCI: Move pci_rebar_size_to_bytes() and export it Ilpo Järvinen
2025-09-11  7:55 ` [PATCH 04/11] PCI: Improve Resizable BAR functions kernel doc Ilpo Järvinen
2025-09-11  8:24   ` Christian König
2025-09-11  8:59     ` Ilpo Järvinen
2025-09-11  9:08       ` Christian König
2025-09-11 20:58   ` Randy Dunlap
2025-09-11  7:55 ` [PATCH 05/11] PCI: Add pci_rebar_size_supported() helper Ilpo Järvinen
2025-09-11  8:27   ` Christian König [this message]
2025-09-11  7:56 ` [PATCH 06/11] drm/i915/gt: Use pci_rebar_size_supported() Ilpo Järvinen
2025-09-11  7:56 ` [PATCH 07/11] drm/xe/vram: Use PCI rebar helpers in resize_vram_bar() Ilpo Järvinen
2025-09-11  7:56 ` [PATCH 08/11] PCI: Add pci_rebar_get_max_size() Ilpo Järvinen
2025-09-11  7:56 ` [PATCH 09/11] drm/xe/vram: Use pci_rebar_get_max_size() Ilpo Järvinen
2025-09-11  7:56 ` [PATCH 10/11] drm/amdgpu: " Ilpo Järvinen
2025-09-11  7:56 ` [PATCH 11/11] PCI: Convert BAR sizes bitmasks to u64 Ilpo Järvinen
2025-09-11  8:35 ` [PATCH 00/11] PCI: Resizable BAR improvements Christian König

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=75167aa2-d974-44ec-9aa5-1a18acdfc091@amd.com \
    --to=christian.koenig@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=bhelgaas@google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=kw@linux.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lucas.demarchi@intel.com \
    --cc=michal.winiarski@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tursulin@ursulin.net \
    /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