From: Stephen Hemminger <stephen@networkplumber.org>
To: Danny Zhou <danny.zhou@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Declan Doherty <declan.doherty@intel.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] UIO pci-generic support broke igb_uio
Date: Tue, 14 Apr 2015 18:06:20 -0700 [thread overview]
Message-ID: <20150414180620.03deb8ee@urahara> (raw)
The addition of uio pci-generic broke use if igb_uio because
the wrong file descriptor is being used.
If I was a hard ass I would recommend uio pci-generic support
be reverted from 2.0 until/unless this fixed.
Failure mode is on startup:
EAL: Error reading interrupts status for fd 0
PANIC in start_port()
rte_eth-dev_start: port=0 err=-5
The problem commit is:
commit 4a499c64959074ba6fa6a5a2b3a2a6aa10627fa1
Author: Danny Zhou <danny.zhou@intel.com>
Date: Fri Feb 20 16:59:15 2015 +0000
eal/linux: enable uio_pci_generic support
Change the EAL PCI code so that it can work with both the
uio_pci_generic in-tree driver, as well as the igb_uio
DPDK-specific driver.
This involves changes to
1) Modify method of retrieving BAR resource mapping information
2) Mapping using resource files in /sys rather than /dev/uio*
2) Setup bus master bit in NIC's PCIe configuration space for
uio_pci_generic.
Signed-off-by: Danny Zhou <danny.zhou@intel.com>
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Declan Doherty <declan.doherty@intel.com>
next reply other threads:[~2015-04-15 1:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 1:06 Stephen Hemminger [this message]
2015-04-15 7:19 ` Zhou, Danny
2015-04-15 15:57 ` Stephen Hemminger
2015-04-15 16:34 ` [dpdk-dev] [PATCH 0/2] fix UIO support broken by 2.0 Stephen Hemminger
2015-04-15 16:36 ` [dpdk-dev] [PATCH 1/2 kernel] uio: add irq control support to uio_pci_generic Stephen Hemminger
2015-04-15 16:38 ` [dpdk-dev] [PATCH 2/2 dpdk] uio: fix pci generic driver breakage Stephen Hemminger
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=20150414180620.03deb8ee@urahara \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=danny.zhou@intel.com \
--cc=declan.doherty@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).