Skip to contentSkip to conversation

can not detected device when use meson build dpdk

dpdk-dev [email protected] 1 participant 2 messages Jul 7, 2020 – Jul 13, 2020

lore
Share & tools
lore
#0 lore raw

https://bugs.dpdk.org/show_bug.cgi?id=503

            Bug ID: 503
           Summary: can not detected device when use meson build dpdk
           Product: DPDK
           Version: 20.08
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: meson
          Assignee: [email protected]
          Reporter: [email protected]

Target Milestone: ---

os:
ubuntu18.04 4.15.0-101-generic x86_64 GNU/Linux

step:

$ cd dpdk
$ ./devtools/test-meson-builds.sh
$ ./build-x86-default/app/dpdk-testpmd -c 0xf -n 4 -- -i
EAL: Detected 112 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: No free hugepages reported in hugepages-2048kB
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL:   using IOMMU type 1 (Type 1)
EAL: Failed to map pci BAR3
EAL:   0000:18:00.0 mapping BAR3 failed: Success
EAL: Requested device 0000:18:00.0 cannot be used
EAL: Failed to map pci BAR3
EAL:   0000:18:00.1 mapping BAR3 failed: Success
EAL: Requested device 0000:18:00.1 cannot be used
EAL: No legacy callbacks, legacy socket not created
testpmd: No probed ethernet devices
Interactive-mode selected
testpmd: create a new mbuf pool <mbuf_pool_socket_0>: n=171456, size=2176,
socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
Done

first bad commit id:
commit 2fd3567e542595d38deea7c186ee52621a46dc99

Author: Tal Shnaiderman <[email protected]>
Date:   Mon Jun 29 15:37:34 2020 +0300

pci: use OS generic memory mapping functions

Changing all of PCIs Unix memory mapping to the new memory allocation API wrapper.

Change all of PCI mapping function usage in
bus/pci to support the new API.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.