From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f175.google.com (mail-wr0-f175.google.com [209.85.128.175]) by dpdk.org (Postfix) with ESMTP id DEC7537AF for ; Thu, 30 Mar 2017 22:20:21 +0200 (CEST) Received: by mail-wr0-f175.google.com with SMTP id l43so78181647wre.1 for ; Thu, 30 Mar 2017 13:20:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=COQCkjd8xjt08r7jVonMrWoPGHuZPKhwbYE4raLmBKI=; b=vpkre8puXniWvhYawpYdW2alK8XKcPHEyujmqdKW5vIfcrnKGwUCiD0c4NPJ8pviVf 7KkPmK8A3dBET4pGkeKHjsSTWp+DGCeIXlR8neBc8u1sX/xpxbSMYKlLDCT1wvNKsNWU B+7UgVyD9AyZ4s2ra4io6g5ulzlfpajgJsdxG4useirtzILwF1pI5VXnCTkbe/ot9+BZ VQPnaY+IiX/W10hoEURyuk0Wy35FcZO1ExZjn3IOCOVMcHqQKs2t/BfgyvsHSUnGvFrg QFp3vFjhutA5I1ZUIaYAw2hu3A6W9WYB3KzaX+vWDllrt4Zh76wG05gHA7AaECf9eM5h VQKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=COQCkjd8xjt08r7jVonMrWoPGHuZPKhwbYE4raLmBKI=; b=LyUm2+xWQ8U33XUw3hFcyx4dbbGtbPRC/WDDRMCaGwHyG1Iriqg2/0KccN/chpU+1Y 2bgv+QYWOrYYr0JwgJFSVy97YYf/x7HUm4oOTkEOH6mm1i+yCwUNnA8auQdNrYydF5U9 MI8XFbBbSCWyrFctoMiPg5O+HMRW1OtRD91lJTrsVNKI0lE2zQurc6rm51C1pI6Edcsw 63w0HGxjyi6wVXAcVQ2XDPFZJ91sJdqVltjQUPd2uM4egwTRJ0MOBQzpnwernmx+UGEV r949WhKY8ZmATy+YCpxDNoudWQwMEbyMLa1neaUnHje9xn3Ekd38hCotpo1UkJU9f1XF RkHw== X-Gm-Message-State: AFeK/H0sz/ko7pisF/wP2inTi/53HTWo/Fl+9o9vdEyT8FjTncDQsoIZATvttKA5hMn5KDHD X-Received: by 10.223.136.92 with SMTP id e28mr1317794wre.73.1490905221625; Thu, 30 Mar 2017 13:20:21 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id o66sm177251wmg.33.2017.03.30.13.20.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 13:20:20 -0700 (PDT) From: Thomas Monjalon To: Alejandro Lucero Cc: Ferruh Yigit , dev@dpdk.org Date: Thu, 30 Mar 2017 22:20:20 +0200 Message-ID: <3492683.SxtYo7vtD0@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <6b4adfde-4e43-07d9-6fcb-43454f1d2d20@intel.com> References: <1484742475-41005-1-git-send-email-alejandro.lucero@netronome.com> <6b4adfde-4e43-07d9-6fcb-43454f1d2d20@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] igb_uio: map dummy dma forcing iommu domain attachment X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2017 20:20:22 -0000 2017-02-17 12:29, Ferruh Yigit: > On 1/18/2017 12:27 PM, Alejandro Lucero wrote: > > For using a DPDK app when iommu is enabled, it requires to > > add iommu=pt to the kernel command line. But using igb_uio driver > > makes DMAR errors because the device has not an IOMMU domain. > > > > Since kernel 3.15, iommu=pt requires to use the internal kernel > > DMA API for attaching the device to the IOMMU 1:1 mapping, aka > > si_domain. Previous versions did attach the device to that > > domain when intel iommu notifier was called. > > > > This is not a problem if the driver does later some call to the > > DMA API because the mapping can be done then. But DPDK apps do > > not use that DMA API at all. > > > > Doing this dma map and unmap is harmless even when iommu is not > > enabled at all. > > > > Signed-off-by: Alejandro Lucero > > Acked-by: Ferruh Yigit > > (I suggest getting this early in 17.05 release, so it can be tested more) Sorry, I've missed it in early days of 17.05. Let's add it now. Ferruh, Alejandro, do not hesitate to ping next time. Applied, thanks