[dpdk-dev] [PATCH] bus/pci: support segment value as address domain on Windows

Dmitry Kozlyuk dmitry.kozliuk at gmail.com
Thu Sep 10 19:57:00 CEST 2020


On Thu, 10 Sep 2020 07:30:39 +0000, Tal Shnaiderman wrote:
> Right, it can happen in virtualization setups when several virtual functions can have the same BDF, e.g.: 
> 
> PS  > Get-NetAdapterHardwareInfo
> 
> Name                           Segment Bus Device Function Slot NumaNode PcieLinkSpeed
> ----                           ------- --- ------ -------- ---- -------- -------------
> Ethernet                                   0   0     10       0                      Unknown
> Ethernet 4                       58601   0      2        0             0       Unknown
> Ethernet 5                       52956   0      2        0             0       Unknown
> 
> DPDK currently can detect either Ethernet 4 or ethernet 5 if only BDF is checked.
> Unix uses the Domain value, the equivalent value for Windows is Segment.

Hi Tal,

I wonder how exactly this setup can be reproduced, i.e. could you
share relevant QEMU options, VMX file or some other config you're using?
Patch idea and code look clear, however, I never managed to build QEMU PCIe
hierarchy to see it working.


More information about the dev mailing list