linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Pierre Morel <pmorel@linux.ibm.com>, Bjorn Helgaas <bhelgaas@google.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	linux-s390@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/5] PCI: Clean up pci_scan_slot()
Date: Thu, 30 Jun 2022 15:48:02 +0200	[thread overview]
Message-ID: <7741c617519b786750fbe04029fbb6295c8d6c85.camel@linux.ibm.com> (raw)
In-Reply-To: <17c30662-7285-0e1a-91fb-071fa2cfc733@linux.ibm.com>

On Thu, 2022-06-30 at 14:40 +0200, Pierre Morel wrote:
> 
> On 6/28/22 16:30, Niklas Schnelle wrote:
> > While determining the next PCI function is factored out of
> > pci_scan_slot() into next_fn() the former still handles the first
> > function as a special case. This duplicates the code from the scan loop.
> > 
> > Furthermore the non ARI branch of next_fn() is generally hard to
> > understand and especially the check for multifunction devices is hidden
> > in the handling of NULL devices for non-contiguous multifunction. It
> > also signals that no further functions need to be scanned by returning
> > 0 via wraparound and this is a valid function number.
> > 
> > Improve upon this by transforming the conditions in next_fn() to be
> > easier to understand.
> > 
> > By changing next_fn() to return -ENODEV instead of 0 when there is no
> > next function we can then handle the initial function inside the loop
> > and deduplicate the shared handling. This also makes it more explicit
> > that only function 0 must exist.
> > 
> > No functional change is intended.
> > 
> > Cc: Jan Kiszka <jan.kiszka@siemens.com>
> > Signed-off-by: Niklas Schnelle <schnelle@linux.ibm.com>
> > ---
> >   drivers/pci/probe.c | 38 +++++++++++++++++++-------------------
> >   1 file changed, 19 insertions(+), 19 deletions(-)
> > 
> > diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> > index 17a969942d37..b05d0ed83a24 100644
> > --- a/drivers/pci/probe.c
> > +++ b/drivers/pci/probe.c
> > @@ -2579,8 +2579,7 @@ struct pci_dev *pci_scan_single_device(struct pci_bus *bus, int devfn)
> >   }
> >   EXPORT_SYMBOL(pci_scan_single_device);
> >   
> > -static unsigned int next_fn(struct pci_bus *bus, struct pci_dev *dev,
> > -			    unsigned int fn)
> > +static int next_fn(struct pci_bus *bus, struct pci_dev *dev, int fn)
> >   {
> >   	int pos;
> >   	u16 cap = 0;
> > @@ -2588,24 +2587,26 @@ static unsigned int next_fn(struct pci_bus *bus, struct pci_dev *dev,
> >   
> >   	if (pci_ari_enabled(bus)) {
> >   		if (!dev)
> > -			return 0;
> > +			return -ENODEV;
> >   		pos = pci_find_ext_capability(dev, PCI_EXT_CAP_ID_ARI);
> >   		if (!pos)
> > -			return 0;
> > +			return -ENODEV;
> >   
> >   		pci_read_config_word(dev, pos + PCI_ARI_CAP, &cap);
> >   		next_fn = PCI_ARI_CAP_NFN(cap);
> >   		if (next_fn <= fn)
> > -			return 0;	/* protect against malformed list */
> > +			return -ENODEV;	/* protect against malformed list */
> >   
> >   		return next_fn;
> >   	}
> >   
> > -	/* dev may be NULL for non-contiguous multifunction devices */
> > -	if (!dev || dev->multifunction)
> > -		return (fn + 1) % 8;
> > +	if (fn >= 7)
> > +		return -ENODEV;
> > +	/* only multifunction devices may have more functions */
> > +	if (dev && !dev->multifunction)
> > +		return -ENODEV;
> >   
> > -	return 0;
> > +	return fn + 1;
> 
> No more % 8 ?
> Even it disapear later shouldn't we keep it ?

The "% 8" became unnecessary due to the explicit "if (fn >= 7)"
above.
The original "% 8" did what I referred to in the commit message with
"It [the function] also signals that no further functions need to be
scanned by returning 0 via wraparound and this is a valid function
number.". Instead we now explicitly return -ENODEV in this case.

> 
> 
> 
> >   }
> >   
> >   static int only_one_child(struct pci_bus *bus)
> > @@ -2643,26 +2644,25 @@ static int only_one_child(struct pci_bus *bus)
> >    */
> >   int pci_scan_slot(struct pci_bus *bus, int devfn)
> >   {
> > -	unsigned int fn, nr = 0;
> >   	struct pci_dev *dev;
> > +	int fn = 0, nr = 0;
> >   
> >   	if (only_one_child(bus) && (devfn > 0))
> >   		return 0; /* Already scanned the entire slot */
> >   
> > -	dev = pci_scan_single_device(bus, devfn);
> > -	if (!dev)
> > -		return 0;
> > -	if (!pci_dev_is_added(dev))
> > -		nr++;
> > -
> > -	for (fn = next_fn(bus, dev, 0); fn > 0; fn = next_fn(bus, dev, fn)) {
> > +	do {
> >   		dev = pci_scan_single_device(bus, devfn + fn);
> >   		if (dev) {
> >   			if (!pci_dev_is_added(dev))
> >   				nr++;
> > -			dev->multifunction = 1;
> > +			if (fn > 0)
> > +				dev->multifunction = 1;
> > +		} else if (fn == 0) {
> > +			/* function 0 is required */
> > +			break;
> >   		}
> > -	}
> > +		fn = next_fn(bus, dev, fn);
> > +	} while (fn >= 0);
> >   
> >   	/* Only one slot has PCIe device */
> >   	if (bus->self && nr)
> > 
> 
> Otherwise LGTM
> 

Thanks for taking a look!


  reply	other threads:[~2022-06-30 13:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 14:30 [PATCH v6 0/5] PCI: Rework pci_scan_slot() and isolated PCI functions Niklas Schnelle
2022-06-28 14:30 ` [PATCH v6 1/5] PCI: Clean up pci_scan_slot() Niklas Schnelle
2022-06-30 12:40   ` Pierre Morel
2022-06-30 13:48     ` Niklas Schnelle [this message]
2022-06-30 14:50       ` Pierre Morel
2022-07-11  8:52         ` Niklas Schnelle
2022-06-28 14:30 ` [PATCH v6 2/5] PCI: Split out next_ari_fn() from next_fn() Niklas Schnelle
2022-06-30 12:44   ` Pierre Morel
2022-06-28 14:30 ` [PATCH v6 3/5] PCI: Move jailhouse's isolated function handling to pci_scan_slot() Niklas Schnelle
2022-06-30 12:47   ` Pierre Morel
2022-06-28 14:30 ` [PATCH v6 4/5] PCI: Extend isolated function probing to s390 Niklas Schnelle
2022-06-30 12:45   ` Pierre Morel
2022-07-01 14:42     ` Niklas Schnelle
2022-07-22 21:13   ` Bjorn Helgaas
2022-06-28 14:31 ` [PATCH v6 5/5] s390/pci: allow zPCI zbus without a function zero Niklas Schnelle
2022-06-30 12:53   ` Pierre Morel
2022-07-22 21:07 ` [PATCH v6 0/5] PCI: Rework pci_scan_slot() and isolated PCI functions Bjorn Helgaas

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=7741c617519b786750fbe04029fbb6295c8d6c85.camel@linux.ibm.com \
    --to=schnelle@linux.ibm.com \
    --cc=bhelgaas@google.com \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mjrosato@linux.ibm.com \
    --cc=pmorel@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).