DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4] doc: add known issue for iommu and igb_uio
Date: Wed, 17 Dec 2014 10:01:39 +0000	[thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C2049C2599@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <1418639563-3599-1-git-send-email-sergio.gonzalez.monroy@intel.com>

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Sergio Gonzalez Monroy
> Sent: Monday, December 15, 2014 10:33 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v4] doc: add known issue for iommu and igb_uio
> 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>

Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>

 I have applied the patch to my tree next/dpdk-doc.

      reply	other threads:[~2014-12-17 10:01 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     ` [dpdk-dev] [PATCH v4] " Sergio Gonzalez Monroy
2014-12-17 10:01       ` Iremonger, Bernard [this message]

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=8CEF83825BEC744B83065625E567D7C2049C2599@IRSMSX107.ger.corp.intel.com \
    --to=bernard.iremonger@intel.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).