All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Alex Chiang <achiang@hp.com>,
	jbarnes@virtuousgeek.org, linux-arch@vger.kernel.org,
	Kyle McMartin <kyle@mcmartin.ca>, Tony Luck <tony.luck@intel.com>,
	Russell King <linux@arm.linux.org.uk>,
	Arnd Bergmann <arnd@arndb.de>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Jeff Dike <jdike@addtoit.com>,
	linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
	David Howells <dhowells@redhat.com>,
	Paul Mundt <lethal@linux-sh.org>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Ingo Molnar <mingo@redhat.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] PCI: remove pcibios_scan_all_fns()
Date: Mon, 22 Jun 2009 11:20:24 -0700	[thread overview]
Message-ID: <4A3FCB68.3030004@goop.org> (raw)
In-Reply-To: <20090622143431.GT19977@parisc-linux.org>

On 06/22/09 07:34, Matthew Wilcox wrote:
> On Mon, Jun 22, 2009 at 08:08:07AM -0600, Alex Chiang wrote:
>   
>> This was #define'd as 0 on all platforms, so let's get rid of it.
>>
>> This change makes pci_scan_slot() slightly easier to read.
>>     
>
>   
>> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
>> index f1ae247..b613cad 100644
>> --- a/drivers/pci/probe.c
>> +++ b/drivers/pci/probe.c
>> @@ -1056,8 +1056,7 @@ int pci_scan_slot(struct pci_bus *bus, int devfn)
>>  	if (dev && !dev->is_added)	/* new device? */
>>  		nr++;
>>  
>> -	if ((dev && dev->multifunction) ||
>> -	    (!dev && pcibios_scan_all_fns(bus, devfn))) {
>> +	if (dev && dev->multifunction) {
>>  		for (fn = 1; fn < 8; fn++) {
>>  			dev = pci_scan_single_device(bus, devfn + fn);
>>  			if (dev) {
>>     
>
> What a good idea.  I was just looking at making this more complicated
> (due to the ARI capability).
>
> I'd like to know what the KVM / Xen / ... people think about this.
> I don't know if they rely on function 5 being able to show up out of
> the blue.
>   

We want to be able to export specific functions to a particular domain,
so it might see a PCI device with only function 5.

It looks like we lose that ability with this patch, is that right?

    J

  reply	other threads:[~2009-06-22 18:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 14:08 [PATCH] PCI: remove pcibios_scan_all_fns() Alex Chiang
2009-06-22 14:21 ` Kyle McMartin
2009-06-22 14:26 ` Ralf Baechle
2009-06-22 14:36   ` Matthew Wilcox
2009-06-22 14:34 ` Matthew Wilcox
2009-06-22 18:20   ` Jeremy Fitzhardinge [this message]
2009-06-22 18:30     ` Matthew Wilcox
2009-06-22 23:40       ` Benjamin Herrenschmidt
2009-06-23 19:08         ` Matthew Wilcox
2009-06-23 20:34           ` Jeremy Fitzhardinge
2009-06-23 20:56             ` Matthew Wilcox
2009-06-23 21:49             ` Benjamin Herrenschmidt
2009-06-23 22:24               ` Jeremy Fitzhardinge
2009-06-23 22:41                 ` Benjamin Herrenschmidt
2009-06-23 22:53                   ` Jeremy Fitzhardinge
2009-06-24  0:02                     ` Benjamin Herrenschmidt
2009-06-24 10:30             ` Ian Campbell
2009-06-24 10:30               ` Ian Campbell
2009-06-23 21:47           ` Benjamin Herrenschmidt
2009-06-22 23:55       ` Jeremy Fitzhardinge
2009-06-23  0:33         ` Benjamin Herrenschmidt
2009-06-23  1:43   ` Chris Wright
2009-06-23  2:22     ` Benjamin Herrenschmidt
2009-06-23 18:29   ` Avi Kivity
2009-06-22 15:29 ` Russell King - ARM Linux
2009-06-22 16:53 ` Arnd Bergmann
2009-06-23 16:43 ` Paul Mundt
2009-06-29 20:33 ` Jesse Barnes

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=4A3FCB68.3030004@goop.org \
    --to=jeremy@goop.org \
    --cc=achiang@hp.com \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jdike@addtoit.com \
    --cc=kyle@mcmartin.ca \
    --cc=lethal@linux-sh.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=matthew@wil.cx \
    --cc=mingo@redhat.com \
    --cc=ralf@linux-mips.org \
    --cc=tony.luck@intel.com \
    --cc=ysato@users.sourceforge.jp \
    /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.