From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 36DC61B1AB for ; Thu, 11 Oct 2018 12:08:15 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9DE4D21221; Thu, 11 Oct 2018 06:08:14 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 11 Oct 2018 06:08:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=8G63+oPZrARbB9e923EgWEKY8FeqKT0ZV6teYqEbYCs=; b=ON0jcWkc7EWR x7/2rJabYWYYVW8LNneCTCY0R7VTEheMnp3osRCHU57+YWn0B+VuIUaxaaw28Qwb 3cEVRdMhWCNuszmDuGeHEn+GHnmfVHdfTZCpcqPsB3UovhVc2iYGb8IL3Gs1amc9 XeVtf4pj4bZ//L9Dh3F9IcRl9DSQ3mQ= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=8G63+oPZrARbB9e923EgWEKY8FeqKT0ZV6teYqEbY Cs=; b=UzpCSYMsAU9G4LaWmVHub6eRvXYnNIhmvpnZgPuO8z8hpxoHM8er4XmHA eLVXPsYfuA3u0aCNmCYkuzqXuQXObGuUDxNm8Igu0f6vjG7nNRUScAp34LuMvpid 7D9JB/DfYyR+wVKCnCY8v4fCKgGdKzxaaMSPDaCTAEOkgnhctpQVHNyu5moLvoB8 JZyq17TALFU+iUkEG3ziWkD+nTDeGLeAyt4RCyvmkXjMdIz4+iIZW2scP7hP4EFC gAuHGgYg9XKDD1IIPjzS84hQqUnWGTMNAL4Kc7hf/bb11kmz5oCxvM659TPW74eF v4Hs3gK5pggzHvyD/hwNVrcM0NExQ== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 6F9E3E435E; Thu, 11 Oct 2018 06:08:11 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Cc: "Burakov, Anatoly" , eric zhang , john.mcnamara@intel.com, allain.legacy@windriver.com, matt.peters@windriver.com, stephen@networkplumber.org, ferruh.yigit@intel.com, arybchenko@solarflare.com, maxime.coquelin@redhat.com, shahafs@mellanox.com, jerin.jacob@caviumnetworks.com, hemant.agrawal@nxp.com, david.marchand@6wind.com Date: Thu, 11 Oct 2018 12:08:10 +0200 Message-ID: <3464472.yQ3oHpXKXX@xps> In-Reply-To: References: <1538599994-23331-1-git-send-email-eric.zhang@windriver.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 0/3] force IOVA to a particular mode 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, 11 Oct 2018 10:08:15 -0000 +Cc more maintainers in order to collect more reviews 04/10/2018 11:19, Burakov, Anatoly: > On 03-Oct-18 9:53 PM, eric zhang wrote: > > This patchset introduces an EAL command line option "--iova-mode" > > to give the user a facility to force IOVA mode to a special value. > > > > Auto detection of the IOVA mode, based on probing the bus and IOMMU > > configuration, may not report the desired addressing mode when virtual > > devices that are not directly attached to the bus are present. > > The EAL command line option "--iova-mode" can be used to select either > > physical addressing('pa') or virtual addressing('va'). > > Acked-by: Anatoly Burakov