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 95FE5A0471 for ; Tue, 16 Jul 2019 12:56:59 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 5102E2BF4; Tue, 16 Jul 2019 12:56:58 +0200 (CEST) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) by dpdk.org (Postfix) with ESMTP id F352CA3 for ; Tue, 16 Jul 2019 12:56:56 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id A241F519; Tue, 16 Jul 2019 06:56:55 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 16 Jul 2019 06:56:56 -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=ChciN4My7ZDWpFOYY3uH4kxKrF3CeDDkzR0lAWd0LcU=; b=Vdmh3gtJ2fRf 0/2lR+sJ5wpPyn5ebthp9c0zfgkJYmigcsDXLj5qcElK5b92dzRhwAb18VQJGCTz hbayF5//eicn858Ly4Kp/efbzZgBI7u3AB/ARAHr8JoOOTkCUcWxSnovg5N/2hAZ 0k+Tmqdo5kCybyw5cyO8f1kOkGwy6v4= 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=fm3; bh=ChciN4My7ZDWpFOYY3uH4kxKrF3CeDDkzR0lAWd0L cU=; b=P7tmybz1N3PWfzI++E6MJYWadMVr2i6FelNwWTqtgIVjCOnPmWe4OwyiC XbCdaRd98H5T2dqalNFxejON1ZgTBbNuu+zVzhzOwUHPxS4SD70zqbD+deyAV4hm xGXmI0jDDSUewwi+oGo667HoTAafhjBfQnsp299ujgrIUmF/dtw4lHROteHe4xhE khHjxQFhXiyW71Ff9t2yAm+uZoh7WNJAxhWOBZ1jdS/thFYh2lnEtPI2Q5poMyLZ dmqNtkmxHM3Jxu9nweQHzqg5/UJnq6dMvJdzOVa65oMq7+2jOejmD5FWlaHFw8DG kSuE747NfNsGeTgBsjjlXIZKIHibA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddriedtgdefiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd 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 B49D9380087; Tue, 16 Jul 2019 06:56:53 -0400 (EDT) From: Thomas Monjalon To: Takeshi Yoshimura Cc: dev@dpdk.org, David Christensen , Burakov@dpdk.org, Anatoly , David Christensen , Pradeep Satyanarayana Date: Tue, 16 Jul 2019 12:56:52 +0200 Message-ID: <2496149.faZSPxUDDV@xps> In-Reply-To: <5b04e7ba-1778-db57-0b87-825f765605bd@linux.vnet.ibm.com> References: <20190614074904.5106-1-tyos@jp.ibm.com> <20190713011532.9426-1-tyos@jp.ibm.com> <5b04e7ba-1778-db57-0b87-825f765605bd@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3] vfio: fix expanding DMA area in ppc64le 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" 16/07/2019 02:20, David Christensen: > > In ppc64le, expanding DMA areas always fail because we cannot remove > > a DMA window. As a result, we cannot allocate more than one memseg in > > ppc64le. This is because vfio_spapr_dma_mem_map() doesn't unmap all > > the mapped DMA before removing the window. This patch fixes this > > incorrect behavior. > > > > I also fixed the order of ioctl for unregister and unmap. The ioctl > > for unregister sometimes report device busy errors due to the > > existence of mapped area. > > > > Signed-off-by: Takeshi Yoshimura > > --- > Acked-by: David Christensen Applied, thanks