DPDK usage discussions
 help / color / mirror / Atom feed
From: "José Miguel Guzmán" <jmguzman@whitestack.com>
To: users@dpdk.org
Subject: [dpdk-users] Binding X722 in Ubuntu
Date: Tue, 14 Apr 2020 02:31:17 -0400	[thread overview]
Message-ID: <CABBAKdwCAnWvzzWKGiMV6abJmzsH5Rkxj+n84MHy9Vhpw1EGjQ@mail.gmail.com> (raw)

Hi
I am trying to bind Intel X722 NICs, but it is not working in Ubuntu 18.04


*root@hyper02:~# ./dpdk-devbind.py -s*
Network devices using DPDK-compatible driver
============================================
<none>

Network devices using kernel driver
===================================
0000:1c:00.0 'Ethernet Controller 10G X550T' if=eno1 drv=ixgbe
unused=vfio-pci
0000:1c:00.1 'Ethernet Controller 10G X550T' if=eno2 drv=ixgbe
unused=vfio-pci
0000:60:00.0 'Ethernet Connection X722 for 10GbE SFP+' if=enp96s0f0
drv=i40e unused=vfio-pci
0000:60:00.1 'Ethernet Connection X722 for 10GbE SFP+' if=enp96s0f1
drv=i40e unused=vfio-pci
. . . .


*root@hyper02:~# ./dpdk-devbind.py -b vfio-pci 0000:60:00.0 *Error: bind
failed for 0000:60:00.0 - Cannot bind to driver vfio-pci
Error: unbind failed for 0000:60:00.0 - Cannot open
/sys/bus/pci/drivers//unbind

What am I missing?


*root@hyper02:~# uname -a*
Linux hyper02 5.0.0-44-generic #48~18.04.1-Ubuntu SMP Wed Mar 18 09:11:43
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux


*root@hyper02:~# cat /proc/cmdline *BOOT_IMAGE=/vmlinuz-5.0.0-44-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro default_hugepagesz=2M
hugepagesz=2M hugepages=53248 transparent_hugepage=never iommu=pt
intel_iommu=on isolcpus=16,17,34,35,52,53,70,71

*root@hyper02:~# modinfo vfio_pci*
filename:
/lib/modules/5.0.0-44-generic/kernel/drivers/vfio/pci/vfio-pci.ko
description:    VFIO PCI - User Level meta-driver
author:         Alex Williamson <alex.williamson@redhat.com>
license:        GPL v2
version:        0.2
srcversion:     96BFF0777823471DD68104B
depends:        vfio,irqbypass,vfio_virqfd
retpoline:      Y
intree:         Y
name:           vfio_pci
vermagic:       5.0.0-44-generic SMP mod_unload
signat:         PKCS#7
signer:
sig_key:
sig_hashalgo:   md4
parm:           ids:Initia
# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.0.0-44-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv
ro default_hugepagesz=2M hugepagesz=2M hugepages=53248
transparent_hugepage=never iommu=pt intel_iommu=on
isolcpus=16,17,34,35,52,53,70,71
l PCI IDs to add to the vfio driver, format is
"vendor:device[:subvendor[:subdevice[:class[:class_mask]]]]" and multiple
comma separated entries can be specified (string)
parm:           nointxmask:Disable support for PCI 2.3 style INTx masking.
If this resolves problems for specific devices, report lspci -vvvxxx to
linux-pci@vger.kernel.org so the device can be fixed automatically via the
broken_intx_masking flag. (bool)
parm:           disable_vga:Disable VGA resource access through vfio-pci
(bool)
parm:           disable_idle_d3:Disable using the PCI D3 low power state
for idle, unused devices (bool)

*lspci -v*
60:00.0 Ethernet controller: Intel Corporation Ethernet Connection X722 for
10GbE SFP+ (rev 04)
Subsystem: Intel Corporation Ethernet Network Adapter X722-2
Flags: fast devsel, IRQ 36, NUMA node 0
Memory at ba000000 (64-bit, prefetchable) [size=16M]
Memory at bc008000 (64-bit, prefetchable) [size=32K]
Expansion ROM at bc280000 [disabled] [size=512K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable- Count=129 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [e0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number d8-b3-8e-ff-ff-1e-f2-f8
Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
Capabilities: [1a0] Transaction Processing Hints
Capabilities: [1b0] Access Control Services
Kernel modules: i40e


Thanks a lot
JM

                 reply	other threads:[~2020-04-14  8:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CABBAKdwCAnWvzzWKGiMV6abJmzsH5Rkxj+n84MHy9Vhpw1EGjQ@mail.gmail.com \
    --to=jmguzman@whitestack.com \
    --cc=users@dpdk.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;
as well as URLs for NNTP newsgroup(s).