From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id CFC49A00E6 for ; Tue, 16 Apr 2019 16:39:22 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id C2BAD1B4DE; Tue, 16 Apr 2019 16:39:22 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 5EAE61B4D8 for ; Tue, 16 Apr 2019 16:39:21 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C76653002F52; Tue, 16 Apr 2019 14:39:20 +0000 (UTC) Received: from rh.redhat.com (ovpn-117-214.ams2.redhat.com [10.36.117.214]) by smtp.corp.redhat.com (Postfix) with ESMTP id E90261001DE0; Tue, 16 Apr 2019 14:39:19 +0000 (UTC) From: Kevin Traynor To: Anatoly Burakov Cc: dpdk stable Date: Tue, 16 Apr 2019 15:37:19 +0100 Message-Id: <20190416143719.21601-61-ktraynor@redhat.com> In-Reply-To: <20190416143719.21601-1-ktraynor@redhat.com> References: <20190416143719.21601-1-ktraynor@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.40]); Tue, 16 Apr 2019 14:39:20 +0000 (UTC) Subject: [dpdk-stable] patch 'vfio: document multiprocess limitation for container API' has been queued to LTS release 18.11.2 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" Hi, FYI, your patch has been queued to LTS release 18.11.2 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 04/24/19. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Thanks. Kevin Traynor --- >From ae959092c95221583d968a0628d31cccb7519d3d Mon Sep 17 00:00:00 2001 From: Anatoly Burakov Date: Wed, 27 Feb 2019 15:41:24 +0000 Subject: [PATCH] vfio: document multiprocess limitation for container API [ upstream commit 1fd3bcf3f97b219a93456466cb1aa46e2419f051 ] Currently, there is no support for sharing custom VFIO containers between multiple processes, but it is not documented. Document this limitation. Signed-off-by: Anatoly Burakov --- lib/librte_eal/common/include/rte_vfio.h | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/lib/librte_eal/common/include/rte_vfio.h b/lib/librte_eal/common/include/rte_vfio.h index cae96fab9..4b3a91e91 100644 --- a/lib/librte_eal/common/include/rte_vfio.h +++ b/lib/librte_eal/common/include/rte_vfio.h @@ -292,4 +292,8 @@ rte_vfio_get_group_fd(int iommu_group_num); * any container created by this API. * + * @note When creating containers using this API, the container will only be + * available in the process that has created it. Sharing containers and + * devices between multiple processes is not supported. + * * @return * the container fd if successful -- 2.20.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2019-04-16 15:34:27.903072801 +0100 +++ 0061-vfio-document-multiprocess-limitation-for-container-.patch 2019-04-16 15:34:25.238178663 +0100 @@ -1,15 +1,15 @@ -From 1fd3bcf3f97b219a93456466cb1aa46e2419f051 Mon Sep 17 00:00:00 2001 +From ae959092c95221583d968a0628d31cccb7519d3d Mon Sep 17 00:00:00 2001 From: Anatoly Burakov Date: Wed, 27 Feb 2019 15:41:24 +0000 Subject: [PATCH] vfio: document multiprocess limitation for container API +[ upstream commit 1fd3bcf3f97b219a93456466cb1aa46e2419f051 ] + Currently, there is no support for sharing custom VFIO containers between multiple processes, but it is not documented. Document this limitation. -Cc: stable@dpdk.org - Signed-off-by: Anatoly Burakov --- lib/librte_eal/common/include/rte_vfio.h | 4 ++++