From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by dpdk.org (Postfix) with ESMTP id 247538045 for ; Fri, 12 Dec 2014 14:28:21 +0100 (CET) Received: by mail-wi0-f173.google.com with SMTP id r20so2480252wiv.12 for ; Fri, 12 Dec 2014 05:28:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:reply-to:organization :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=RQEz//HjoSheuz6tUUc7qJDljgJ/hHr69WktmPKok5g=; b=ZtoeacWw32A+vi8i6upYH7RpPSutSgwr0QPb5PHuEeA0hXy7F/4JycxvkD3oycVSCE YBUJeYkdDY97oWjvNmvQ+ucDJYGOO0Y1WyOyqQRLi/t1zo4HhN8Ut3/WJiH5jTKlJ3xG SVEIXTbwXtM0iyn5Mb7LqeP1LUJC4XKEDDbnH0MdyhsdEm3ugf5o4Z00/Yr3AYnvGWbH 7hAl41JWaglYVu6iWabF/qoeB5BW0KEhG2T9kAXfDUU/1x5JfokbKqfTnkb3gXVV1EY7 vUPv4Gl42yQh6r0EmKxv2pTxgycl26iWS1lLp+I70rjG7ObJwPmBef1ATjP1n5/0IoDZ d/nA== X-Gm-Message-State: ALoCoQnV9Ab39ah1pyNMrzHih0Q/99q+opNXNosbQGGaConvkxP9x1BZLRtvsZDaeKk7MuerQwim X-Received: by 10.180.72.199 with SMTP id f7mr7773263wiv.58.1418390900831; Fri, 12 Dec 2014 05:28:20 -0800 (PST) Received: from ?IPv6:2a01:e35:8b63:dc30:e8f2:d06a:212d:2c36? ([2a01:e35:8b63:dc30:e8f2:d06a:212d:2c36]) by mx.google.com with ESMTPSA id bs2sm1824485wjc.43.2014.12.12.05.28.19 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Dec 2014 05:28:20 -0800 (PST) Message-ID: <548AED73.3030804@6wind.com> Date: Fri, 12 Dec 2014 14:28:19 +0100 From: Nicolas Dichtel Organization: 6WIND User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: "Gonzalez Monroy, Sergio" , "dev@dpdk.org" References: <1418380884-6875-1-git-send-email-sergio.gonzalez.monroy@intel.com> <1418385971-17323-1-git-send-email-sergio.gonzalez.monroy@intel.com> <548AE6BC.7060202@6wind.com> <91383E96CE459D47BCE92EFBF5CE73B004EFED22@IRSMSX108.ger.corp.intel.com> In-Reply-To: <91383E96CE459D47BCE92EFBF5CE73B004EFED22@IRSMSX108.ger.corp.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH v2] doc: add known issue for iommu and igb_uio X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: nicolas.dichtel@6wind.com List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 13:28:21 -0000 Le 12/12/2014 14:20, Gonzalez Monroy, Sergio a écrit : >> 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. Ok, I was not sure that the last version was tested ;-) > >>> 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 I think it's a very useful info. Thank you, Nicolas