From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4164CA046B for ; Thu, 25 Jul 2019 11:38:19 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 39A851C2D0; Thu, 25 Jul 2019 11:38:18 +0200 (CEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id CD8F21C2CA for ; Thu, 25 Jul 2019 11:38:16 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jul 2019 02:38:16 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,306,1559545200"; d="scan'208";a="193751262" Received: from aburakov-mobl1.ger.corp.intel.com (HELO [10.237.220.83]) ([10.237.220.83]) by fmsmga004.fm.intel.com with ESMTP; 25 Jul 2019 02:38:14 -0700 To: David Marchand Cc: dev , Jerin Jacob Kollanukkaran , Thomas Monjalon References: <5d8f83fb7dd574d83a044c6a01e2613798f256c3.1563986790.git.anatoly.burakov@intel.com> <61fe76fd-beb8-6074-32e1-16b47170a6ef@intel.com> From: "Burakov, Anatoly" Message-ID: Date: Thu, 25 Jul 2019 10:38:14 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] eal: pick IOVA as PA if IOMMU is not available 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 25-Jul-19 10:35 AM, David Marchand wrote: > On Thu, Jul 25, 2019 at 11:31 AM Burakov, Anatoly > wrote: >> >> On 25-Jul-19 9:05 AM, David Marchand wrote: >>> On Wed, Jul 24, 2019 at 6:46 PM Anatoly Burakov >>> wrote: >>>> >>>> When IOMMU is not available, /sys/kernel/iommu_groups will not be >>>> populated. This is happening since at least 3.6 when VFIO support >>>> was added. If the directory is empty, EAL should not pick IOVA as >>>> VA as the default IOVA mode. >>>> >>>> We also assume that VFIO equals IOMMU, so if VFIO support is not >>>> compiled, we always assume IOMMU support is not available. >>> >>> Not sure I agree with this statement. >>> What about unknown (from eal pov) kernel drivers? >> >> Are there any cases where we can use IOVA as VA mode without having VFIO >> compiled? > > If a pmd relies on a kernel driver we don't know in EAL. > This is not the case afaik, but I'd prefer we don't mix vfio and iommu. > OK, i can drop that. -- Thanks, Anatoly