From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Dichtel Subject: Re: [PATCH v2] doc: add known issue for iommu and igb_uio Date: Fri, 12 Dec 2014 13:59:40 +0100 Message-ID: <548AE6BC.7060202@6wind.com> References: <1418380884-6875-1-git-send-email-sergio.gonzalez.monroy@intel.com> <1418385971-17323-1-git-send-email-sergio.gonzalez.monroy@intel.com> Reply-To: nicolas.dichtel-pdR9zngts4EAvxtiuMwx3w@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable To: Sergio Gonzalez Monroy , dev-VfR2kkLFssw@public.gmane.org Return-path: In-Reply-To: <1418385971-17323-1-git-send-email-sergio.gonzalez.monroy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" Le 12/12/2014 13:06, Sergio Gonzalez Monroy a =C3=A9crit : > 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 > --- 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 Regards, Nicolas