All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Xu, Rosen" <rosen.xu@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "gaetan.rivet@6wind.com" <gaetan.rivet@6wind.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"Pei, Yulong" <yulong.pei@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH] doc/guides/rel_notes: Add known issue for IOMMU attributes read
Date: Wed, 16 May 2018 06:08:11 +0000	[thread overview]
Message-ID: <0E78D399C70DA940A335608C6ED296D739FECBDD@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <6b9962cf-1b50-0cf7-83e6-d9fe696c62bf@intel.com>

Hi Anatoly,

> -----Original Message-----
> From: Burakov, Anatoly
> Sent: Tuesday, May 15, 2018 1:10
> To: Xu, Rosen <rosen.xu@intel.com>; dev@dpdk.org
> Cc: gaetan.rivet@6wind.com; Mcnamara, John <john.mcnamara@intel.com>;
> Pei, Yulong <yulong.pei@intel.com>; stable@dpdk.org
> Subject: Re: [PATCH] doc/guides/rel_notes: Add known issue for IOMMU
> attributes read
> 
> On 14-May-18 11:44 AM, Rosen Xu wrote:
> > Read IOMMU attributes from linux kernle 4.10.0 error.
> 
> s/kernle/kernel :)

Fixed
 
> >
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Rosen Xu <rosen.xu@intel.com>
> > ---
> >   doc/guides/rel_notes/known_issues.rst | 21 +++++++++++++++++++++
> >   1 file changed, 21 insertions(+)
> >
> > diff --git a/doc/guides/rel_notes/known_issues.rst
> > b/doc/guides/rel_notes/known_issues.rst
> > index afcc2c4..74876ff 100644
> > --- a/doc/guides/rel_notes/known_issues.rst
> > +++ b/doc/guides/rel_notes/known_issues.rst
> > @@ -714,3 +714,24 @@ igb_uio can not be used when running l3fwd-
> power
> >
> >   **Driver/Module**:
> >      ``igb_uio`` module.
> > +
> > +
> > +linux kernel iommu attribute read error
> 
> Should this be capitalized?

Fixed
 
> > +---------------------------------------
> > +
> > +**Description**:
> > +   Read immu attributes from /sys/devices/virtual/iommu/dmarXXX/intel-
> iommu/cap in linux kernel
> > +   4.10.0 error. That because the link between the iommu sysfs-device and
> the struct intel_iommu
> > +   is no longer stored as driver-data.
> 
> s/immu/IOMMU/, and i think this needs to be rewritten to something like as
> follows:
> 
> Reading IOMMU attributes from

Fixed

> /sys/devices/virtual/iommu/dmarXXX/intel-iommu/cap in Linux kernel
> 4.10.0 results in an error. This is because the link between the IOMMU sysfs-
> device and struct intel_iommu is no longer stored as driver-data.
> 
> (i have no idea what that last sentence means, maybe someone could help
> provide a better explanation?)

This linux kernel issue is fixed, around the 4.10/4.11 timeframe.
commit a7fdb6e648fb10a4174483b5fc4dac9c25bd2093
Author: Joerg Roedel <jroedel@suse.de>
Date:   Tue Feb 28 13:57:18 2017 +0100

    iommu/vt-d: Fix crash when accessing VT-d sysfs entries
    
    The link between the iommu sysfs-device and the struct
    intel_iommu is no longer stored as driver-data. Update the
    code to use the new access method.
 
> > +
> > +**Implication**:
> > +   When insmod ``vfio-pci`` and running testpmd APP, it doesn't initiate
> properly.
> 
> Should probably be reworded as follows:
> 
> When binding devices to VFIO and attempting to run testpmd application,
> testpmd (and other DPDK applications) will not initialize.

Fixed.
 
> > +
> > +**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.
> >
> 
> 
> --
> Thanks,
> Anatoly

  reply	other threads:[~2018-05-16  6:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 10:44 [PATCH] doc/guides/rel_notes: Add known issue for IOMMU attributes read Rosen Xu
2018-05-14 17:10 ` Burakov, Anatoly
2018-05-16  6:08   ` Xu, Rosen [this message]
2018-05-16  7:29 ` [PATCH v2] " Rosen Xu
2018-05-28 15:31   ` Mcnamara, John
2018-05-28 15:36     ` Mcnamara, John
2018-05-29  0:25       ` Xu, Rosen
2018-05-30 12:04       ` [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=0E78D399C70DA940A335608C6ED296D739FECBDD@SHSMSX104.ccr.corp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.