DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
To: "nicolas.dichtel@6wind.com" <nicolas.dichtel@6wind.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] doc: add known issue for iommu and igb_uio
Date: Fri, 12 Dec 2014 13:20:18 +0000	[thread overview]
Message-ID: <91383E96CE459D47BCE92EFBF5CE73B004EFED22@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <548AE6BC.7060202@6wind.com>

> From: Nicolas Dichtel [mailto:nicolas.dichtel@6wind.com]
> Sent: Friday, December 12, 2014 1:00 PM
> 
> Le 12/12/2014 13:06, Sergio Gonzalez Monroy a écrit :
> > Known issue regarding iommu/VT-d and igb_uio on Linux kernel version
> > 3.15 to 3.17 where unbinding the device from the driver removes the
> > 1:1
> Do you mean that the problem doesn't exist with a linux 3.18?
> 
Yes,  as it is mentioned in the resolution/workarounds, earlier or later kernels do solve the issue.

> > mapping for the device on the iommu resulting in memory access errors.
> Do you have the linux commit id which introduces the problem? And the one
> which solves it?
> 
I do have the commits, but I was not sure if I should add the info (at least no previous release note did).

Introduced in:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/iommu/intel-iommu.c?id=816997d03bca9fabcee65f3481eb0297103eceb7

Solved in:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/iommu/intel-iommu.c?id=1196c2fb0407683c2df92d3d09f9144d42830894

> >
> > Signed-off-by: Sergio Gonzalez Monroy
> > <sergio.gonzalez.monroy@intel.com>
> > ---
> Please, also don't forget to explain what you have changed between the v1
> and v2.
> The history should be put here, after the '---', something like:
> 
> v2: update that
> 
I did forget. I will add it for v3.
I need to fix issue with patch not  showing in patchwork (I think cause of R (registered) symbol in context line).

Regards,
Sergio
> 
> Regards,
> Nicolas

  reply	other threads:[~2014-12-12 13:20 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 [this message]
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     ` [dpdk-dev] [PATCH v4] " Sergio Gonzalez Monroy
2014-12-17 10:01       ` 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=91383E96CE459D47BCE92EFBF5CE73B004EFED22@IRSMSX108.ger.corp.intel.com \
    --to=sergio.gonzalez.monroy@intel.com \
    --cc=dev@dpdk.org \
    --cc=nicolas.dichtel@6wind.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).