From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v4] doc: add known issue for iommu and igb_uio
Date: Mon, 15 Dec 2014 10:32:43 +0000 [thread overview]
Message-ID: <1418639563-3599-1-git-send-email-sergio.gonzalez.monroy@intel.com> (raw)
In-Reply-To: <1418395427-17406-1-git-send-email-sergio.gonzalez.monroy@intel.com>
Known issue regarding iommu/VT-d and igb_uio in Linux kernel version 3.15
to 3.17 where unbinding the device from the driver removes the 1:1 mapping
in the iommu resulting in IOMMU/DMAR errors when the device tries to
access memory.
Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
---
v4:
Improve commit log description
Add kernel error message info
Improve formatting
Fix patch charset encoding
v3:
Remove reference number
Add Linux commit links
v2:
Fix title uppercase
Add extra blank line to show proper indentation
v1:
Known igb_uio issue when iommu/vt-d is on
doc/guides/rel_notes/known_issues.rst | 32 ++++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 8ef654a..d26dcfa 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -1026,3 +1026,35 @@ Stopping the port does not down the link on Intel® 40G ethernet controller
| Driver/Module | Poll Mode Driver (PMD) |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
+
+Devices bound to igb_uio with VT-d enabled do not work on Linux* kernel 3.15-3.17
+---------------------------------------------------------------------------------
+
++--------------------------------+--------------------------------------------------------------------------------------+
+| Title | Devices bound to igb_uio with VT-d enabled do not work on Linux* kernel 3.15-3.17 |
++================================+======================================================================================+
+| Description | | When VT-d is enabled (iommu=pt intel_iommu=on), devices are 1:1 mapped. |
+| | In the Linux* kernel unbinding devices from drivers removes that mapping which |
+| | result in IOMMU errors. |
+| | | Introduced in Linux `kernel 3.15 commit <https://git.kernel.org/cgit/linux/kernel/ |
+| | git/torvalds/linux.git/commit/drivers/iommu/ |
+| | intel-iommu.c?id=816997d03bca9fabcee65f3481eb0297103eceb7>`_, |
+| | solved in Linux `kernel 3.18 commit <https://git.kernel.org/cgit/linux/kernel/git/ |
+| | torvalds/linux.git/commit/drivers/iommu/ |
+| | intel-iommu.c?id=1196c2fb0407683c2df92d3d09f9144d42830894>`_. |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Implication | | Devices will not be allowed to access memory, resulting in following kernel errors:|
+| | | ``dmar: DRHD: handling fault status reg 2`` |
+| | | ``dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr a0c58000`` |
+| | | ``DMAR:[fault reason 02] Present bit in context entry is clear`` |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Resolution/ Workaround | | Use earlier or later kernel versions, or avoid driver binding on boot by |
+| | blacklisting the driver modules. |
+| | | ie. in the case of ixgbe, we can pass the kernel command line option: |
+| | | ``modprobe.blacklist=ixgbe`` |
+| | | This way we do not need to unbind the device to bind it to igb_uio. |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Affected Environment/ Platform | Linux* systems with kernel versions 3.15 to 3.17 |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Driver/Module | igb_uio module |
++--------------------------------+--------------------------------------------------------------------------------------+
--
1.9.3
next prev parent reply other threads:[~2014-12-15 10:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 10:41 [dpdk-dev] [PATCH] doc: Add " Sergio Gonzalez Monroy
2014-12-12 12:06 ` [dpdk-dev] [PATCH v2] doc: add " Sergio Gonzalez Monroy
2014-12-12 12:59 ` Nicolas Dichtel
2014-12-12 13:20 ` Gonzalez Monroy, Sergio
2014-12-12 13:28 ` Nicolas Dichtel
2014-12-12 13:38 ` Gonzalez Monroy, Sergio
2014-12-12 13:50 ` Nicolas Dichtel
2014-12-12 16:34 ` Thomas Monjalon
2014-12-12 14:43 ` [dpdk-dev] [PATCH v3] " Sergio Gonzalez Monroy
2014-12-15 10:32 ` Sergio Gonzalez Monroy [this message]
2014-12-17 10:01 ` [dpdk-dev] [PATCH v4] " Iremonger, Bernard
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=1418639563-3599-1-git-send-email-sergio.gonzalez.monroy@intel.com \
--to=sergio.gonzalez.monroy@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).