DPDK patches and discussions
 help / color / mirror / Atom feed
From: Rosen Xu <rosen.xu@intel.com>
To: dev@dpdk.org
Cc: anatoly.burakov@intel.com, gaetan.rivet@6wind.com,
	john.mcnamara@intel.com, rosen.xu@intel.com,
	yulong.pei@intel.com, stable@dpdk.org
Subject: [dpdk-dev] [PATCH v2] doc/guides/rel_notes: Add known issue for IOMMU attributes read
Date: Wed, 16 May 2018 15:29:12 +0800	[thread overview]
Message-ID: <1526455752-147108-1-git-send-email-rosen.xu@intel.com> (raw)
In-Reply-To: <1526294652-102665-1-git-send-email-rosen.xu@intel.com>

Linux kernel 4.10.0 iommu attribute read error

Cc: stable@dpdk.org

Signed-off-by: Rosen Xu <rosen.xu@intel.com>

v2 updates:
===========
 - Fixed Anatoly comments
---
 doc/guides/rel_notes/known_issues.rst | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index afcc2c4..716bd73 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -714,3 +714,28 @@ igb_uio can not be used when running l3fwd-power
 
 **Driver/Module**:
    ``igb_uio`` module.
+
+
+Linux kernel 4.10.0 iommu attribute read error
+----------------------------------------------
+
+**Description**:
+   When VT-d is enabled (``iommu=pt intel_iommu=on``), reading IOMMU attributes from
+   /sys/devices/virtual/iommu/dmarXXX/intel-iommu/cap on Linux kernel 4.10.0 error.
+   This bug is fixed in `Linux commmit a7fdb6e648fb
+   <https://patchwork.kernel.org/patch/9595727/>`_,
+   This bug is introduced in `Linux commmit 39ab9555c241
+   <https://patchwork.kernel.org/patch/9554403/>`_,
+
+**Implication**:
+   When binding devices to VFIO and attempting to run testpmd application,
+   testpmd (and other DPDK applications) will not initialize.
+
+**Resolution/Workaround**:
+   Use other linux kernel version. It only happens in linux kernel 4.10.0.
+
+**Affected Environment/Platform**:
+   ALL OS of linux kernel 4.10.0.
+
+**Driver/Module**:
+   ``vfio-pci`` module.
-- 
1.8.3.1

  parent reply	other threads:[~2018-05-16  7:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 10:44 [dpdk-dev] [PATCH] " Rosen Xu
2018-05-14 17:10 ` Burakov, Anatoly
2018-05-16  6:08   ` Xu, Rosen
2018-05-16  7:29 ` Rosen Xu [this message]
2018-05-28 15:31   ` [dpdk-dev] [PATCH v2] " Mcnamara, John
2018-05-28 15:36     ` Mcnamara, John
2018-05-29  0:25       ` Xu, Rosen
2018-05-30 12:04       ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon

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=1526455752-147108-1-git-send-email-rosen.xu@intel.com \
    --to=rosen.xu@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=gaetan.rivet@6wind.com \
    --cc=john.mcnamara@intel.com \
    --cc=stable@dpdk.org \
    --cc=yulong.pei@intel.com \
    /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).