答复: PCI bus do 2 Enumeration when 2 root bridges under 1 host bridge

[Eric Song <EricSong@zhaoxin.com>]

Hi, Laszlo
        Many thanks for rapidly reply.
        Your analyze is very clear. But while the PciBusDxe driver is binding a root bridge, why the PciBusDxe driver do host bridge enumeration. It is illogical.
        Even though it maybe has no side effect, it is confused for users.

Thanks
Eric

-----邮件原件-----
发件人: Laszlo Ersek [mailto:lersek@redhat.com]
发送时间: 2017年8月17日 17:19
收件人: Eric Song; edk2-devel@lists.01.org
抄送: Tiger Liu; Ni, Ruiyu
主题: Re: [edk2] [EDK2] PCI bus do 2 Enumeration when 2 root bridges under 1 host bridge

Adding Ray

On 08/17/17 06:50, Eric Song wrote:
> Hi, experts
> If there is 2 root bridges under 1 host bridge on the PCI hierarchy,
> whether EDK2 Pci bus driver can support it ? the answer is YES, but
> some confused things in it.
>
> 1)       On BDS phase, ConnectController is called for every root
> bridge, so Pci bus start() will be called for every root bridge.
>
>   VisitAllInstancesOfProtocol (&gEfiPciRootBridgeIoProtocolGuid,
> ConnectRootBridge, NULL);
>
> 2)       In PCI bus driver, Pci start() will do enumeration on the
> entire host bridge
>
> PciEnumerator()->PciHostBridgeEnumerator->\x1dPciResAlloc->GetNextRootBri
> dge()
>
> That means Do enumeration on entire host bridge for every one root
> bridge. So there are 2 enumerations on entire host bridge for my PCI
> hierarchy.
> What I confused is why do 2 enumerations on entire host bridge by
> every one root bridge. Since BDS connect controller by one root bridge
> , Pci bus driver should enumerate corresponding root bridge, But it do
> the entire host bridge which is the parent of the root bridge. Or BDS
> should connect controller by one host bridge, then it will match the
> pci bus driver \x18s enumeration policy. In a word, I think it is
> illogical for current EDKII code.
>
> Well, the current code execution will do 2 enumerations on host bridge
> for 2 root bridges under 1 host bridge. Even though 2rd enumeration
> would be not full enumeration, but do PciEnumeratorLight(), I think it
> is still not necessary. Whether there is any side effect ? In another
> word, current PCI bus driver enumeration can\x19t be Suitable for 2 root
> bridges under 1 host bridge or not? It indeed match the PCI hierarchy
> of 2 host bridges and 1 root bridge under 1 host bridge.

While I don't know the internals of this host bridge-level enumeration, it is worth looking at:

(a) in what context PciEnumerator() is called, and

(b) how PciEnumerator() works across multiple calls.

Regarding (a): PciEnumerator() is called from PciBusDriverBindingStart(), that is, when the PciBusDxe driver is binding a root brirdge. This is the code:

  //
  // Enumerate the entire host bridge
  // After enumeration, a database that records all the device information will be created
  //
  //
  Status = PciEnumerator (Controller);

Regarding (b): the PciEnumerator() function depends on a global variable called "gFullEnumeration". This is what we have at the beginning and at the end of PciEnumerator(), respectively:

  //
  // If PCI bus has already done the full enumeration, never do it again
  //
  if (!gFullEnumeration) {
    return PciEnumeratorLight (Controller);
  }

...

  gFullEnumeration = FALSE;

  Status = gBS->InstallProtocolInterface (
                  &HostBridgeHandle,
                  &gEfiPciEnumerationCompleteProtocolGuid,
                  EFI_NATIVE_INTERFACE,
                  NULL
                  );

The above seems to imply that PciBusDxe needs host bridge-level information to do its job. This information is apparently collected when the first root bridge is bound. When binding further root bridges (under the same host bridge), the same information collecting is not repeated;
PciEnumerator() branches to PciEnumeratorLight() instead.

Hope this helps,
Laszlo


保密声明：
本邮件含有保密或专有信息，仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。
CONFIDENTIAL NOTE:
This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.