patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Anoob Joseph <anoobj@marvell.com>
To: Vipin Varghese <vipin.varghese@amd.com>
Cc: "Ferruh.Yigit@amd.com" <Ferruh.Yigit@amd.com>,
	"cheng1.jiang@intel.com" <cheng1.jiang@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: RE: [EXT] [PATCH v2] app/dma-perf: fix physical address seg-fault
Date: Wed, 16 Aug 2023 10:46:39 +0000	[thread overview]
Message-ID: <PH0PR18MB4672028DF8781F3179A4191BDF15A@PH0PR18MB4672.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230816094216.1847-1-vipin.varghese@amd.com>

> 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 <vipin.varghese@amd.com>
> Suggested-by: Anoob Joseph <anoobj@marvell.com>

Acked-by: Anoob Joseph <anoobj@marvell.com>

  parent reply	other threads:[~2023-08-16 10:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16  7:18 [PATCH] " Vipin Varghese
2023-08-16  7:26 ` [EXT] " Anoob Joseph
2023-08-16  7:31   ` Varghese, Vipin
2023-08-16  9:24 ` [PATCH v2] " Vipin Varghese
2023-08-16  9:35 ` Vipin Varghese
2023-08-16  9:42 ` Vipin Varghese
2023-08-16 10:12   ` Jerin Jacob
2023-08-16 10:46   ` Anoob Joseph [this message]
2023-09-21  2:28   ` Jiang, Cheng1
2023-10-04  9:00     ` Varghese, Vipin
2023-10-04 13:00       ` Jerin Jacob
2023-10-19  4:19   ` [PATCH v3] " Vipin Varghese
2023-10-24  2:16     ` lihuisong (C)
2023-11-14 14:27       ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PH0PR18MB4672028DF8781F3179A4191BDF15A@PH0PR18MB4672.namprd18.prod.outlook.com \
    --to=anoobj@marvell.com \
    --cc=Ferruh.Yigit@amd.com \
    --cc=cheng1.jiang@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=vipin.varghese@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).