From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by dpdk.org (Postfix) with ESMTP id 85F7DAD80 for ; Fri, 8 Jul 2016 19:27:38 +0200 (CEST) Received: by mail-wm0-f48.google.com with SMTP id k123so18608011wme.0 for ; Fri, 08 Jul 2016 10:27:38 -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=0a1i78IbK9sUDwtoWF5K/b8Fvb8BI6JLQuFqsswxA1I=; b=epZ+r2s72zJkXCwSjil/WfJhSxcPDab+zgwXtip85iU8PoAAISSs2DuzxZJ6NYdLgp 4Z6SwINT42/w5GXx3Hk86sAYqeSM15JCliZCs9k6TRdy/SUZCZmKu9bHjDJqfnQXL6I4 sf8WOkLJRcMUrwGLYni/eX79b166oNzTd9vYfygyl4ehZEGSVpEShOMFjBd6AmeuoCst sdrH4+9vMT6NVOiN+LixJQn0BX033mWIlE2KaXnu2bMmahYiZBnEbJSQSX8GVaKVd1Bb CBUjyZ3JMF1lkDm/mlNarN3LlaKHmW1SRQhZmKFR8Un0ryXOUqHTEiKnO930uJmVQZgW nj9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=0a1i78IbK9sUDwtoWF5K/b8Fvb8BI6JLQuFqsswxA1I=; b=TnrIb80IwMTRtNy/1orixK6CHBUQvl07NIxIRlqPUrPqENCnRlRi/K/BZWsmHuBu5i 0ZdI10ryJ0zgcf2bbDWf8Ti9e5TpK33pTSJKNM4UIlPS2qWi5UXlfuANFta7+dE7d4B4 0J10mcYlwGnr57M6ugNHZebBQErb9Tqaur7Jb4tNDEI85WA2X4GI7yN4Z+Ioea60hxPB pxBfPAnixnBgqmMP5fbuUpaI7vJma6HSJYmju4+ObksKRbSCwQf6GCvuCnvG/E2xiJ3z x2P9+D1Nss7eBMet9xDPqcLqcEHZSmr3UXJ/B+EnxY3bWJebAMlVSnZGyOxJbCuCxBKH L/ug== X-Gm-Message-State: ALyK8tIuBn250ZZDJiEz3iSa88pxPAac7LrJnP9aLtqiBwawGBKltnmLJYXdueJV7loGwch6 X-Received: by 10.28.138.85 with SMTP id m82mr4745302wmd.88.1467998858287; Fri, 08 Jul 2016 10:27:38 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id n26sm4016846wmi.3.2016.07.08.10.27.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Jul 2016 10:27:37 -0700 (PDT) From: Thomas Monjalon To: Zhe Tao Cc: dev@dpdk.org, Ferruh Yigit , Alejandro Lucero , Stephen Hemminger Date: Fri, 08 Jul 2016 19:27:36 +0200 Message-ID: <2574807.bEb98RZhNN@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <57336AD6.1050809@intel.com> References: <1462879301-13570-1-git-send-email-zhe.tao@intel.com> <57336AD6.1050809@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v1] igu_uio: fix IOMMU domain issue X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 17:27:38 -0000 Ping, this patch is stalled. 2016-05-11 18:24, Ferruh Yigit: > On 5/11/2016 8:35 AM, Alejandro Lucero wrote: > > On Tue, May 10, 2016 at 4:59 PM, Stephen Hemminger < > > stephen@networkplumber.org> wrote: > > > >> On Tue, 10 May 2016 19:21:41 +0800 > >> Zhe Tao wrote: > >> > >>> Problem: > >>> The following operations will cause the igb_uio based DPDK > >>> operation failed. > >>> --Any device assignment through the kvm_assign_device interface, > >>> this can be the pci-assign method in QEMU > >>> --VFIO group attachment operation(attach to the container) > >>> this can happens in vfio-pci assignment in QEMU > >> > >> > >> If you have an IOMMU why not use VFIO instead, it is better. > >> > > > > It is not about VFIO against UIO but about how iommu domains are created > > and destroyed by the (old) kernel when iommu=pt. So even with VFIO you can > > have problems. > > Problem is in IOMMU driver but we are adding a workaround to igb_uio, if > using VFIO solves the issue, I believe that is better workaround. > > 1) Is there any case IOMMU supported but VFIO is not supported? Is there > anything forces to use igb_uio? > > 2) Does using VFIO solves the issue defined in problem statement? > > > > > We have had problems like this and other due to our device (NFP) just > > mapping up to 40 bits of address space. Old kernels used in LTS > > distributions like Ubuntu are iommu buggy and you need to do things like > > this mapping inside the driver for solving problems. By the way, using > > SRIOV just adds more problems. It is not safe to use iommu=pt with 3.13.x > > Ubuntu kernels. > > > > It would be a good thing for the original patch to identify those kernels > > where the problem was detected. Of course, there could be more kernels with > > the same problem but that is more work to do. > > > > Thanks, > ferruh