From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,URIBL_SBL,URIBL_SBL_A, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2C7A0C606B0 for ; Tue, 9 Jul 2019 09:32:34 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id BE5DC214AF for ; Tue, 9 Jul 2019 09:32:33 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BE5DC214AF Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id F2557493D; Tue, 9 Jul 2019 11:32:32 +0200 (CEST) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 16A64A3 for ; Tue, 9 Jul 2019 11:32:30 +0200 (CEST) X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Jul 2019 02:32:29 -0700 X-IronPort-AV: E=Sophos;i="5.63,470,1557212400"; d="scan'208";a="156123416" Received: from bricha3-mobl.ger.corp.intel.com ([10.251.95.59]) by orsmga007-auth.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Jul 2019 02:32:25 -0700 Date: Tue, 9 Jul 2019 10:32:23 +0100 From: Bruce Richardson To: Jerin Jacob Kollanukkaran Cc: David Marchand , dev , Thomas Monjalon , Ben Walker , "Burakov, Anatoly" Message-ID: <20190709093223.GB485@bricha3-MOBL.ger.corp.intel.com> References: <20190708142450.51597-1-jerinj@marvell.com> <20190709083950.GA485@bricha3-MOBL.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) Subject: Re: [dpdk-dev] [EXT] Re: [PATCH] bus/pci: fix IOVA as VA mode selection 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 Tue, Jul 09, 2019 at 09:05:07AM +0000, Jerin Jacob Kollanukkaran wrote: > > -----Original Message----- > > From: Bruce Richardson > > Sent: Tuesday, July 9, 2019 2:10 PM > > To: Jerin Jacob Kollanukkaran > > Cc: David Marchand ; dev ; > > Thomas Monjalon ; Ben Walker > > ; Burakov, Anatoly > > > > Subject: Re: [dpdk-dev] [EXT] Re: [PATCH] bus/pci: fix IOVA as VA mode > > selection > > > > On Mon, Jul 08, 2019 at 07:13:28PM +0000, Jerin Jacob Kollanukkaran wrote: > > > See below, > > > > > > Please send the email as text to avoid formatting issue.(No HTML) > > > > > > From: David Marchand > > > Sent: Tuesday, July 9, 2019 12:09 AM > > > To: Jerin Jacob Kollanukkaran > > > Cc: dev ; Thomas Monjalon ; > > Ben > > > Walker ; Burakov, Anatoly > > > > > > Subject: [EXT] Re: [dpdk-dev] [PATCH] bus/pci: fix IOVA as VA mode > > > selection > > > > > > ________________________________________ > > > > > > On Mon, Jul 8, 2019 at 4:25 PM wrote: > > > From: Jerin Jacob > > > > > > Existing logic fails to select IOVA mode as VA if driver request to > > > enable IOVA as VA. > > > > > > IOVA as VA has more strict requirement than other modes, so enabling > > > positive logic for IOVA as VA selection. > > > > > > This patch also updates the default IOVA mode as PA for PCI devices as > > > it has to deal with DMA engines unlike the virtual devices that may > > > need only IOVA as DC. > > > > > > We have three cases: > > > - driver/hw supports IOVA as PA only > > > > > > [Jerin] It is not driver cap, it is more of system cap(IOMMU vs non > > > IOMMU). We are already addressing that case > > > > > > > Not necessarily. It's possible to have hardware that does not use the IOMMU > > on a platform. Therefore, you have more than two options to support. > > Any example such device? > On further investigation, it appears I was wrong/misinformed. All devices I'm aware of work fine with an IOMMU if one is one the platform. Please ignore my previous assertion, and thanks for getting me to follow up on this! /Bruce