From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 34E99431EC for ; Tue, 24 Oct 2023 04:16:43 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6452D40298; Tue, 24 Oct 2023 04:16:41 +0200 (CEST) Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by mails.dpdk.org (Postfix) with ESMTP id A44F44014F; Tue, 24 Oct 2023 04:16:39 +0200 (CEST) Received: from kwepemm000004.china.huawei.com (unknown [172.30.72.54]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4SDwZ74bjYzVm2N; Tue, 24 Oct 2023 10:12:47 +0800 (CST) Received: from [10.67.121.59] (10.67.121.59) by kwepemm000004.china.huawei.com (7.193.23.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Tue, 24 Oct 2023 10:16:27 +0800 Message-ID: Date: Tue, 24 Oct 2023 10:16:26 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 Subject: Re: [PATCH v3] app/dma-perf: fix physical address seg-fault To: Vipin Varghese , , , , , References: <20230816094216.1847-1-vipin.varghese@amd.com> <20231019041956.609-1-vipin.varghese@amd.com> From: "lihuisong (C)" In-Reply-To: <20231019041956.609-1-vipin.varghese@amd.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.67.121.59] X-ClientProxiedBy: dggems702-chm.china.huawei.com (10.3.19.179) To kwepemm000004.china.huawei.com (7.193.23.18) X-CFilter-Loop: Reflected X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 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 在 2023/10/19 12:19, Vipin Varghese 写道: > do_cpu_mem_copy uses DPDK API rte_mbuf_data_iova to return > the start of the virtual address for both src and dst. > But in case of iova mode set as PA, this results in seg-fault. > This is because rte_memcpy uses VA address and not PA. > > This fix invokes `rte_pktmbuf_mtod` for both src and dst. > > Bugzilla ID: 1269 > Fixes: 623dc9364dc6 ("app/dma-perf: introduce DMA performance test") > Cc: cheng1.jiang@intel.com > > Cc: stable@dpdk.org > > Signed-off-by: Vipin Varghese > Suggested-by: Anoob Joseph > Suggested-by: Jerin Jacob > Acked-by: Huisong Li