From: Shivaram Mysore <shivaram.mysore@gmail.com>
To: users@dpdk.org
Subject: Re: [dpdk-users] vfio drivers not showing up with dpdk-devbind
Date: Sun, 17 Sep 2017 15:26:17 -0700 [thread overview]
Message-ID: <CAJRY+joTV=vwY=dRzfLUYQekZBqhJoZowGXVXxisL5iPeWchBg@mail.gmail.com> (raw)
In-Reply-To: <CAJRY+jp87D_Cv1EMn5DddRZAwtTj7J7ggNtOFT49N2Mg0WhMSQ@mail.gmail.com>
Issue fixed.
Once I loaded igb_uio module, vfio-pci also got loaded.
I was able to use igb_uio module to bind to DPDK interfaces. They are all
working fine now.
Thanks!
On Sun, Sep 17, 2017 at 12:18 PM, Shivaram Mysore <shivaram.mysore@gmail.com
> wrote:
> Hello,
>
> I am using Ubuntu 17.04 and unable to see vfio-pci in DPDK devices. Any
> ideas as to what I am missing
>
>
> # *lsmod | egrep vfio*
> vfio_pci 45056 0
> vfio_iommu_type1 24576 0
> vfio_virqfd 16384 1 vfio_pci
> vfio 32768 2 vfio_iommu_type1,vfio_pci
> irqbypass 16384 2 kvm,vfio_pci
>
> #* lsmod | egrep uiouio_pci_generic *
> uio_pci_generic 16384 0
> uio 20480 1 uio_pci_generic
>
> #* grep pci /etc/dpdk/interfaces*
> pci 0000:04:00.0 vfio-pci
> pci 0000:04:00.1 uio_pci_generic
> # pci 0000:05:00.0 igb_uio
> # pci 0000:06:00.0 rte_kni
>
> #* cat /proc/cmdline *
> BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=/dev/mapper/ovs--intelsdn--2--vg-root
> ro quiet intel_iommu=on iommu=pt default_hugepagesz=1G hugepagesz=1G
> hugepages=4
>
> #* lscpu*
> Architecture: x86_64
> CPU op-mode(s): 32-bit, 64-bit
> Byte Order: Little Endian
> CPU(s): 88
> On-line CPU(s) list: 0-87
> Thread(s) per core: 2
> Core(s) per socket: 22
> Socket(s): 2
> NUMA node(s): 2
> Vendor ID: GenuineIntel
> CPU family: 6
> Model: 79
> Model name: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
> Stepping: 1
> CPU MHz: 1200.036
> CPU max MHz: 3600.0000
> CPU min MHz: 1200.0000
> BogoMIPS: 4389.51
> Virtualization: VT-x
> L1d cache: 32K
> L1i cache: 32K
> L2 cache: 256K
> L3 cache: 56320K
> NUMA node0 CPU(s): 0-21,44-65
> NUMA node1 CPU(s): 22-43,66-87
> Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
> pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good
> nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl
> vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic
> movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm
> 3dnowprefetch epb cat_l3 cdp_l3 intel_ppin intel_pt tpr_shadow vnmi
> flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms
> invpcid rtm cqm rdt_a rdseed adx smap xsaveopt cqm_llc cqm_occup_llc
> cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts
>
>
> # *dpdk-devbind --status*
>
> Network devices using DPDK-compatible driver
> ============================================
> <none>
>
> Network devices using kernel driver
> ===================================
> 0000:03:00.0 'Ethernet Controller 10-Gigabit X540-AT2' if=eno1 drv=ixgbe
> unused= *Active*
> 0000:03:00.1 'Ethernet Controller 10-Gigabit X540-AT2' if=eno2 drv=ixgbe
> unused=
> 0000:05:00.0 'I350 Gigabit Network Connection' if=ens786f0 drv=igb unused=
> 0000:05:00.1 'I350 Gigabit Network Connection' if=ens786f1 drv=igb unused=
> 0000:05:00.2 'I350 Gigabit Network Connection' if=ens786f2 drv=igb unused=
> 0000:05:00.3 'I350 Gigabit Network Connection' if=ens786f3 drv=igb unused=
> 0000:81:00.0 'I350 Gigabit Network Connection' if=ens787f0 drv=igb unused=
> 0000:81:00.1 'I350 Gigabit Network Connection' if=ens787f1 drv=igb unused=
> 0000:81:00.2 'I350 Gigabit Network Connection' if=ens787f2 drv=igb unused=
> 0000:81:00.3 'I350 Gigabit Network Connection' if=ens787f3 drv=igb unused=
> 0000:83:00.0 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens802f0
> drv=i40e unused=
> 0000:83:00.1 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens802f1
> drv=i40e unused=
>
> Other network devices
> =====================
> <none>
>
> Crypto devices using DPDK-compatible driver
> ===========================================
> <none>
>
> Crypto devices using kernel driver
> ==================================
> 0000:09:00.0 'DH895XCC Series QAT' drv=dh895xcc unused=qat_dh895xcc
>
> Other crypto devices
> ====================
> <none>
>
> #
>
>
>
prev parent reply other threads:[~2017-09-17 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 19:18 Shivaram Mysore
2017-09-17 22:26 ` Shivaram Mysore [this message]
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='CAJRY+joTV=vwY=dRzfLUYQekZBqhJoZowGXVXxisL5iPeWchBg@mail.gmail.com' \
--to=shivaram.mysore@gmail.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).