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 AF1AA4D3A for ; Mon, 29 Oct 2018 00:04:08 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4853121F82; Sun, 28 Oct 2018 19:04:08 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 28 Oct 2018 19:04:08 -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=xl9Sh+tc0js5kSpOTcojUWnz8CSYAD9IKfDFo9zs1x0=; b=li2EOUw1967z n9LBgMV1DFqJQ1+3+VGGSyQPrIrX4rdbY0//r5q0xx4dVqd8XJbFK6wGIxFgxkcz KDaQbn9B2KztM44AkeLFr+eBKe72usfMdbrn0CVcm4fZe2dq8lxPAhz5vVDT3CCp lMd4A1n9G1XnhaHfZ6/WjlMfVZRvWKg= 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=xl9Sh+tc0js5kSpOTcojUWnz8CSYAD9IKfDFo9zs1 x0=; b=riFWnszBGGqY2O7/lE/C2p4GI1EgtUa5oINDjVG2sXA21DeWdiZW+pcdR h4164K8THGD3drZWGv5UpoeILpCe52C2IOEXOyIbI0I2GkbIE+4gttJTf/NbnZWe u2drb3xNpuugKp7N7aVPD8Bs2zkC38ELVAqFJ0L7M9lXIaMY8dDWaudRfS7JIOMc vYQXm6W6ISOJegyW94G3zJ569Kf+LU8r7yt/jj/jPWLz90DsqB9pUMbEWkWKUaJG v0r2+2kv5eHy698r844RElHDHA3IL60ohyChQdg7pxvN3MJK9PM0UEDWjWdZq/UX 9f6oTcxoco5ym8KO9cCjr01/qeNnA== 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 16D35E4412; Sun, 28 Oct 2018 19:04:05 -0400 (EDT) From: Thomas Monjalon To: eric zhang Cc: dev@dpdk.org, "Burakov, Anatoly" , 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: Mon, 29 Oct 2018 00:04:11 +0100 Message-ID: <1870558.97lydUBT9V@xps> In-Reply-To: <3464472.yQ3oHpXKXX@xps> References: <1538599994-23331-1-git-send-email-eric.zhang@windriver.com> <3464472.yQ3oHpXKXX@xps> 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: Sun, 28 Oct 2018 23:04:08 -0000 11/10/2018 12:08, Thomas Monjalon: > +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 Rebased and applied, thanks