From: Thomas Gleixner <tglx@linutronix.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Jan Kiszka <jan.kiszka@siemens.com>,
Benedikt Spranger <b.spranger@linutronix.de>,
Lukas Wunner <lukas@wunner.de>
Subject: Re: x86/PCI: Scan all functions during probing
Date: Wed, 24 Aug 2016 10:39:11 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1608241037510.5714@nanos> (raw)
In-Reply-To: <20160818203348.GK27353@localhost>
On Thu, 18 Aug 2016, Bjorn Helgaas wrote:
> I looked up the spec: PCI (not PCIe) r3.0, sec 3.2.2.3.4, says:
>
> A single-function device may optionally respond to all function
> numbers as the same function or may ... respond only to function 0
> and not respond to the other function numbers.
>
> I'm concerned that a single-function device that responds to all
> function numbers might break with this patch.
>
> [multi-function devices] are also required to always implement
> function 0 in the device.
>
> Here's the reason we can advance by 8 in the "Go find them" loop.
>
> If a single function device is detected (i.e., bit 7 in the Header
> Type register of function 0 is 0), no more functions for that Device
> Number will be checked. If a multi-function device is detected
> (i.e., bit 7 in the Header Type register of function 0 is 1), then
> all remaining Function Numbers will be checked.
>
> This patch does the opposite of what the first sentence recommends.
Fair enough. We'll need to find a way to deal with that in jailhouse then.
Thanks,
tglx
next prev parent reply other threads:[~2016-08-24 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 11:22 x86/PCI: Scan all functions during probing Thomas Gleixner
2016-08-09 12:13 ` Lukas Wunner
2016-08-09 13:44 ` Bjorn Helgaas
2016-08-18 20:33 ` Bjorn Helgaas
2016-08-24 8:39 ` Thomas Gleixner [this message]
2016-08-24 11:13 ` Jan Kiszka
2016-08-24 17:23 ` Thomas Gleixner
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=alpine.DEB.2.20.1608241037510.5714@nanos \
--to=tglx@linutronix.de \
--cc=b.spranger@linutronix.de \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=x86@kernel.org \
/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