DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>,  dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] doc: add known issue for iommu and igb_uio
Date: Fri, 12 Dec 2014 13:59:40 +0100	[thread overview]
Message-ID: <548AE6BC.7060202@6wind.com> (raw)
In-Reply-To: <1418385971-17323-1-git-send-email-sergio.gonzalez.monroy@intel.com>

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?

> 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?

> 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
The history should be put here, after the '---', something like:

v2: update that


  reply	other threads:[~2014-12-12 12:59 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 [this message]
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     ` [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=548AE6BC.7060202@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=dev@dpdk.org \
    --cc=sergio.gonzalez.monroy@intel.com \


* 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).