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 87DE1A04DB; Wed, 2 Dec 2020 06:47:02 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id EDB66C9B8; Wed, 2 Dec 2020 06:46:59 +0100 (CET) Received: from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com [67.231.156.173]) by dpdk.org (Postfix) with ESMTP id A4F0CC9A8 for ; Wed, 2 Dec 2020 06:46:58 +0100 (CET) Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 0B25fSwP013736; Tue, 1 Dec 2020 21:46:56 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=pfpt0220; bh=059B+iYNcCTKgEZRMGqUnuPM4VRcdLb0HVZEbk05dZA=; b=PuBKW+j8mwAbSAHMApwui6FLgB/Fivi2jCI7UHJq57Pkx93+t0KG+XFdU5W1eJqpKWDd nsbxIE2DVfSzQWhjCCnJqtz1XECaufMuuXMs1pUo1+O8n0YzkMZ0J7fXofhbSOczsL8c ssLXhcK3SP1LPZZcvFJULgkoT31F5B31yxuXRurxaf3lc5TE5Xshwal9mhXcHelQtHrM SqYkFOAuLcYbUVKFai/swfuVLVlxSVTblSPAddTpw3gyQYSGpkl3mB1NzfqOxX/sAGUh I/4vsA5fhLFb12smobgwATeCdl6Hcs+QCDSpoJyjri6bTAb8lMt0xWi4ogU6ovVH21EA mQ== Received: from sc-exch03.marvell.com ([199.233.58.183]) by mx0b-0016f401.pphosted.com with ESMTP id 355w5097cm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 01 Dec 2020 21:46:54 -0800 Received: from SC-EXCH04.marvell.com (10.93.176.84) by SC-EXCH03.marvell.com (10.93.176.83) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 1 Dec 2020 21:46:52 -0800 Received: from DC5-EXCH02.marvell.com (10.69.176.39) by SC-EXCH04.marvell.com (10.93.176.84) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 1 Dec 2020 21:46:53 -0800 Received: from maili.marvell.com (10.69.176.80) by DC5-EXCH02.marvell.com (10.69.176.39) with Microsoft SMTP Server id 15.0.1497.2 via Frontend Transport; Tue, 1 Dec 2020 21:46:53 -0800 Received: from hyd1588t430.marvell.com (unknown [10.29.52.204]) by maili.marvell.com (Postfix) with ESMTP id 2CB2A3F7043; Tue, 1 Dec 2020 21:46:50 -0800 (PST) From: Nithin Dabilpuram To: , David Christensen , CC: , , Nithin Dabilpuram Date: Wed, 2 Dec 2020 11:16:43 +0530 Message-ID: <20201202054647.3449-1-ndabilpuram@marvell.com> X-Mailer: git-send-email 2.8.4 In-Reply-To: <20201012081106.10610-1-ndabilpuram@marvell.com> References: <20201012081106.10610-1-ndabilpuram@marvell.com> MIME-Version: 1.0 Content-Type: text/plain X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.312, 18.0.737 definitions=2020-12-02_01:2020-11-30, 2020-12-02 signatures=0 Subject: [dpdk-dev] [PATCH v4 0/4] fix issue with partial DMA unmap 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" Partial DMA unmap is not supported by VFIO type1 IOMMU in Linux. Though the return value is zero, the returned DMA unmap size is not same as expected size. So add test case and fix to both heap triggered DMA mapping and user triggered DMA mapping/unmapping. Refer vfio_dma_do_unmap() in drivers/vfio/vfio_iommu_type1.c Snippet of comment is below. /* * vfio-iommu-type1 (v1) - User mappings were coalesced together to * avoid tracking individual mappings. This means that the granularity * of the original mapping was lost and the user was allowed to attempt * to unmap any range. Depending on the contiguousness of physical * memory and page sizes supported by the IOMMU, arbitrary unmaps may * or may not have worked. We only guaranteed unmap granularity * matching the original mapping; even though it was untracked here, * the original mappings are reflected in IOMMU mappings. This * resulted in a couple unusual behaviors. First, if a range is not * able to be unmapped, ex. a set of 4k pages that was mapped as a * 2M hugepage into the IOMMU, the unmap ioctl returns success but with * a zero sized unmap. Also, if an unmap request overlaps the first * address of a hugepage, the IOMMU will unmap the entire hugepage. * This also returns success and the returned unmap size reflects the * actual size unmapped. * We attempt to maintain compatibility with this "v1" interface, but * we take control out of the hands of the IOMMU. Therefore, an unmap * request offset from the beginning of the original mapping will * return success with zero sized unmap. And an unmap request covering * the first iova of mapping will unmap the entire range. This behavior can be verified by using first patch and add return check for dma_unmap.size != len in vfio_type1_dma_mem_map() v4: - Fixed issue with patch 4/4 on x86 builds. v3: - Fixed external memory test case(4/4) to use system page size instead of 4K. - Fixed check-git-log.sh issue and rebased. - Added acked-by from anatoly.burakov@intel.com to first 3 patches. v2: - Reverted earlier commit that enables mergin contiguous mapping for IOVA as PA. (see 1/3) - Updated documentation about kernel dma mapping limits and vfio module parameter. - Moved vfio test to test_vfio.c and handled comments from Anatoly. Nithin Dabilpuram (4): vfio: revert changes for map contiguous areas in one go vfio: fix DMA mapping granularity for type1 IOVA as VA test: add test case to validate VFIO DMA map/unmap test: change external memory test to use system page sz app/test/meson.build | 1 + app/test/test_external_mem.c | 3 +- app/test/test_vfio.c | 103 +++++++++++++++++++++++++++++++++ doc/guides/linux_gsg/linux_drivers.rst | 10 ++++ lib/librte_eal/linux/eal_vfio.c | 93 ++++++++++++----------------- lib/librte_eal/linux/eal_vfio.h | 1 + 6 files changed, 153 insertions(+), 58 deletions(-) create mode 100644 app/test/test_vfio.c -- 2.8.4