From: Andrew Rybchenko <arybchenko@solarflare.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
Alejandro Lucero <alejandro.lucero@netronome.com>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: [dpdk-dev] vfio: failed to select IOMMU type
Date: Sat, 1 Apr 2017 13:46:45 +0300 [thread overview]
Message-ID: <694e35cd-8c9d-715b-9b6b-482b5c802846@solarflare.com> (raw)
Hi,
after the following commit (it was picked up by dpdk-next-net recently),
I have problems with VFIO:
===
commit 94c0776b1badd1ee715d60f07391058f23494365
Author: Alejandro Lucero <alejandro.lucero@netronome.com>
Date: Wed Mar 29 10:54:50 2017 +0100
vfio: support hotplug
Current device hotplug is just supported by UIO managed devices.
This patch adds same functionality with VFIO.
It has been validated through tests using IOMMU and also with
VFIO and no-iommu mode.
Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
===
The second PCI function fails to bind:
# testpmd -w 06:00.0 -w 06:00.1 -c 0xc -n 4 -- --rxd=512 --txd=512
--crc-strip --disable-hw-vlan-filter --disable-hw-vlan-strip
EAL: Detected 16 lcore(s)
EAL: 2048 hugepages of size 2097152 reserved, but no mounted hugetlbfs
found for that size
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:06:00.0 on NUMA socket 0
EAL: probe driver: 1924:a03 net_sfc_efx
EAL: using IOMMU type 1 (Type 1)
EAL: Ignore mapping IO port bar(0) addr: 2101
EAL: PCI device 0000:06:00.1 on NUMA socket 0
EAL: probe driver: 1924:a03 net_sfc_efx
EAL: 0000:06:00.1 failed to select IOMMU type
EAL: Requested device 0000:06:00.1 cannot be used
EAL: Requested device 0000:7f:08.0 cannot be used
EAL: Requested device 0000:7f:08.2 cannot be used
EAL: Requested device 0000:7f:08.3 cannot be used
...
Also I don't understand why it spams about many other PCI functions
taking into account that just 2 are specified in whitelist.
I've bisected to find commit when the problem appears, but has not found
root cause yet.
Andrew.
next reply other threads:[~2017-04-01 10:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 10:46 Andrew Rybchenko [this message]
2017-04-03 16:11 ` Burakov, Anatoly
2017-04-04 15:29 ` Andrew Rybchenko
2017-04-04 15:52 ` Burakov, Anatoly
2017-04-04 16:10 ` Andrew Rybchenko
2017-04-04 16:20 ` Burakov, Anatoly
2017-04-05 7:15 ` Alejandro Lucero
2017-04-05 7:12 ` Alejandro Lucero
2017-04-06 9:10 ` Burakov, Anatoly
2017-04-18 11:22 ` Alejandro Lucero
2017-04-24 9:09 ` Burakov, Anatoly
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=694e35cd-8c9d-715b-9b6b-482b5c802846@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=alejandro.lucero@netronome.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@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).