public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Michał Winiarski" <michal.winiarski@intel.com>
Cc: linux-pci@vger.kernel.org, intel-xe@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org,
	LKML <linux-kernel@vger.kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Michal Wajdeczko" <michal.wajdeczko@intel.com>,
	"Lucas De Marchi" <lucas.demarchi@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Matt Roper" <matthew.d.roper@intel.com>
Subject: Re: [PATCH v6 5/6] PCI: Allow drivers to control VF BAR size
Date: Wed, 2 Apr 2025 15:04:44 +0300 (EEST)	[thread overview]
Message-ID: <5de3951c-01f1-3892-09e1-f7d30a4e048d@linux.intel.com> (raw)
In-Reply-To: <fnisbg2bng3f5rkcoc7duzi34g7hghcqgzzehc5v6yb772kdj4@rcjs4mftf7s6>

[-- Attachment #1: Type: text/plain, Size: 2714 bytes --]

On Wed, 2 Apr 2025, Michał Winiarski wrote:

> On Wed, Mar 26, 2025 at 05:22:50PM +0200, Ilpo Järvinen wrote:
> > On Thu, 20 Mar 2025, Michał Winiarski wrote:
> > 
> > > Drivers could leverage the fact that the VF BAR MMIO reservation is
> > > created for total number of VFs supported by the device by resizing the
> > > BAR to larger size when smaller number of VFs is enabled.
> > > 
> > > Add a pci_iov_vf_bar_set_size() function to control the size and a
> > > pci_iov_vf_bar_get_sizes() helper to get the VF BAR sizes that will
> > > allow up to num_vfs to be successfully enabled with the current
> > > underlying reservation size.
> > > 
> > > Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>


> > > +/**
> > > + * pci_iov_vf_bar_get_sizes - get VF BAR sizes allowing to create up to num_vfs
> > > + * @dev: the PCI device
> > > + * @resno: the resource number
> > > + * @num_vfs: number of VFs
> > > + *
> > > + * Get the sizes of a VF resizable BAR that can be accommodated within the
> > > + * resource that reserves the MMIO space if num_vfs are enabled.
> > 
> > I'd rephrase to:
> > 
> > Get the sizes of a VF resizable BAR that can be accommodate @num_vfs 
> > within the currently assigned size of the resource @resno.
> 
> Ok.

I have small grammar error in that:

"can be accomodate" -> "can accomodate"

> > > + * defined in the spec (bit 0=1MB, bit 31=128TB).
> > > + */
> > > +u32 pci_iov_vf_bar_get_sizes(struct pci_dev *dev, int resno, int num_vfs)
> > > +{
> > > +	resource_size_t size;
> > > +	u32 sizes;
> > > +	int i;
> > > +
> > > +	sizes = pci_rebar_get_possible_sizes(dev, resno);
> > > +	if (!sizes)
> > > +		return 0;
> > > +
> > > +	while (sizes > 0) {
> > > +		i = __fls(sizes);
> > > +		size = pci_rebar_size_to_bytes(i);
> > > +
> > > +		if (size * num_vfs <= pci_resource_len(dev, resno))
> > > +			break;
> > > +
> > > +		sizes &= ~BIT(i);
> > > +	}
> > 
> > Couldn't this be handled without a loop:
> > 
> > 	bar_sizes = (round_up(pci_resource_len(dev, resno) / num_vfs) - 1) >>
> > 		    ilog2(SZ_1M);
> > 
> > 	sizes &= bar_sizes;
> > 
> > (Just to given an idea, I wrote this into the email so it might contain 
> > some off-by-one errors or like).
> 
> I think the division will need to be wrapped with something like do_div
> (because IIUC, we have 32bit architectures where resource_size_t is
> u64).
> 
> But yeah, we can drop the loop, turning it into something like this:
> 
> 	vf_len = pci_resource_len(dev, resno);
> 	do_div(vf_len, num_vfs);
> 	sizes = (roundup_pow_of_two(vf_len + 1) - 1) >> ilog2(SZ_1M);

Yes, good point, 64-bit division is required.

-- 
 i.

  reply	other threads:[~2025-04-02 12:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-20 11:08 [PATCH v6 0/6] PCI: VF resizable BAR Michał Winiarski
2025-03-20 11:08 ` [PATCH v6 1/6] PCI/IOV: Restore VF resizable BAR state after reset Michał Winiarski
2025-03-26 14:42   ` Ilpo Järvinen
2025-03-26 14:52     ` Ilpo Järvinen
2025-04-02 10:20       ` Michał Winiarski
2025-03-20 11:08 ` [PATCH v6 2/6] PCI: Add a helper to convert between VF BAR number and IOV resource Michał Winiarski
2025-03-26 14:46   ` Ilpo Järvinen
2025-04-02 10:23     ` Michał Winiarski
2025-03-20 11:08 ` [PATCH v6 3/6] PCI: Allow IOV resources to be resized in pci_resize_resource() Michał Winiarski
2025-03-26 14:58   ` Ilpo Järvinen
2025-04-02 10:25     ` Michał Winiarski
2025-03-20 11:08 ` [PATCH v6 4/6] PCI/IOV: Check that VF BAR fits within the reservation Michał Winiarski
2025-03-26 15:11   ` Ilpo Järvinen
2025-03-28 16:39     ` Ilpo Järvinen
2025-04-02 10:33       ` Michał Winiarski
2025-04-02 10:31     ` Michał Winiarski
2025-03-20 11:08 ` [PATCH v6 5/6] PCI: Allow drivers to control VF BAR size Michał Winiarski
2025-03-26 15:22   ` Ilpo Järvinen
2025-04-02 10:43     ` Michał Winiarski
2025-04-02 12:04       ` Ilpo Järvinen [this message]
2025-03-20 11:08 ` [PATCH v6 6/6] drm/xe/pf: Set VF LMEM " Michał Winiarski
2025-03-26 15:29   ` Ilpo Järvinen
2025-04-02 10:44     ` Michał Winiarski

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=5de3951c-01f1-3892-09e1-f7d30a4e048d@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lucas.demarchi@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=michal.wajdeczko@intel.com \
    --cc=michal.winiarski@intel.com \
    --cc=mripard@kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tzimmermann@suse.de \
    /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