From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Issue with igb_uio in Fedora 24
Date: Fri, 1 Jul 2016 10:21:35 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE20258A06F@IRSMSX103.ger.corp.intel.com> (raw)
Hi,
We have seen an issue when using the igb_uio module in Fedora
24. However, it relates to kernel 4.5+ so it could occur in other
distros/oses.
The issue occurs after binding a nic to igb_uio:
# ./tools/dpdk_nic_bind.py -b igb_uio 0000:03:00.0
# ./x86_64-native-linuxapp-gcc/app/test
EAL: Detected 8 lcore(s)
EAL: Probing VFIO support...
PMD: bnxt_rte_pmd_init() called for (null)
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL: probe driver: 8086:1533 rte_igb_pmd
EAL: pci_map_resource():
cannot mmap(39, 0x7f1c51800000, 0x100000, 0x0):
Invalid argument (0xffffffffffffffff)
EAL: Error - exiting with code: 1
Cause: Requested device 0000:03:00.0 cannot be used
The issue is exposed when the kernel is compiled with option
CONFIG_IO_STRICT_DEVMEM turned on.
This option is new from kernel 4.5 and is on by default in Fedora 24:
config IO_STRICT_DEVMEM
bool "Filter I/O access to /dev/mem"
depends on STRICT_DEVMEM
---help---
If this option is disabled, you allow userspace (root) access
to all io-memory regardless of whether a driver is actively
using that range. Accidental access to this is obviously
disastrous, but specific access can be used by people
debugging kernel drivers.
If this option is switched on, the /dev/mem file only allows
userspace access to *idle* io-memory ranges (see /proc/iomem)
This may break traditional users of /dev/mem (dosemu, legacy
X, etc...) if the driver using a given range cannot be
disabled.
If in doubt, say Y.
This issue doesn't occur with uio_pci_generic.
John
next reply other threads:[~2016-07-01 10:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 10:21 Mcnamara, John [this message]
2016-07-01 10:53 ` Ferruh Yigit
2016-07-01 11:35 ` [dpdk-dev] [PATCH] igb_uio: fix mmap failure Ferruh Yigit
2016-07-01 12:47 ` Thomas Monjalon
2016-07-01 14:39 ` Ferruh Yigit
2016-07-01 14:54 ` Thomas Monjalon
2016-07-01 15:07 ` [dpdk-dev] [PATCH v2] igb_uio: fix possible mmap failure for Linux > v4.3 Ferruh Yigit
2016-07-01 15:52 ` De Lara Guarch, Pablo
2016-07-01 15:54 ` Ferruh Yigit
2016-07-01 15:59 ` [dpdk-dev] [PATCH v3] igb_uio: fix possible mmap failure for Linux >= v4.5 Ferruh Yigit
2016-07-05 15:00 ` [dpdk-dev] [PATCH v4] " Ferruh Yigit
2016-07-10 13:58 ` Thomas Monjalon
2016-07-02 0:12 ` [dpdk-dev] Issue with igb_uio in Fedora 24 De Lara Guarch, Pablo
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=B27915DBBA3421428155699D51E4CFE20258A06F@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@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).