patches for DPDK stable branches
 help / color / mirror / Atom feed
From: fengchengwen <fengchengwen@huawei.com>
To: Vipin Varghese <vipin.varghese@amd.com>, <cheng1.jiang@intel.com>,
	<stable@dpdk.org>, <anoobj@marvell.com>, <jerinj@marvell.com>,
	<dev@dpdk.org>
Subject: Re: [PATCH v3] app/dma-perf: fix physical address seg-fault
Date: Thu, 19 Oct 2023 15:13:59 +0800	[thread overview]
Message-ID: <dd214976-f454-a4d6-a782-a279796d4e4f@huawei.com> (raw)
In-Reply-To: <20231019041607.570-1-vipin.varghese@amd.com>

Acked-by: Chengwen Feng <fengchengwen@huawei.com>

On 2023/10/19 12:16, Vipin Varghese wrote:
> 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>
> Suggested-by: Jerin Jacob <jerinj@marvell.com>
> 
> ---

...

  reply	other threads:[~2023-10-19  7:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19  4:16 Vipin Varghese
2023-10-19  7:13 ` fengchengwen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-16  9:42 [PATCH v2] " Vipin Varghese
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=dd214976-f454-a4d6-a782-a279796d4e4f@huawei.com \
    --to=fengchengwen@huawei.com \
    --cc=anoobj@marvell.com \
    --cc=cheng1.jiang@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=stable@dpdk.org \
    --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).