DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vikas Gupta <vikas.gupta@broadcom.com>
To: dev@dpdk.org
Cc: Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>,
	 Vikram Prakash <vikram.prakash@broadcom.com>
Subject: [dpdk-dev] Issue with VFIO/IOMMU
Date: Thu, 3 Sep 2020 16:39:50 +0530	[thread overview]
Message-ID: <e58baac48f6bbe14e2ccba10e68eeace@mail.gmail.com> (raw)


  I observe an issue with IOVA address returned by api
rte_memzone_reserve_aligned (flags= RTE_MEMZONE_IOVA_CONTIG) used for queue
memory allocation. With high level debugging, I notice that IOVA address
returned in mz->iova is not mapped by VFIO_IOMMU_MAP_DMA so in turn SMMU
exception is seen.

*Details for the setup*

Platform: Armv8 (Broadcom Stingray)

DPDK release: DPDK 20.08 <http://fast.dpdk.org/rel/dpdk-20.08.tar.xz>

PMD patch:


dpdk-test is launched using below command

*dpdk-test --vdev <cryptopmd_name> -w 0000:00:00.0 --iova-mode pa *

The test suite is launched over dpdk-test application command prompt using
command ‘cryptodev_<cryptopmd_name>_autotest’

The issue is seen when several iterations of above test_suite is executed
which in turn do multiple calls to rte_memzone_reserve_aligned,
rte_mempool_create and rte_memzone_free, rte_mempool_free.

 Function *vfio_type1_dma_mem_map* with map/unmap event is executed several
times during test_suite run.

Any inputs would be helpful.



             reply	other threads:[~2020-09-03 11:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 11:09 Vikas Gupta [this message]
2020-09-04 13:50 ` Burakov, Anatoly
2020-09-07 13:31   ` Vikas Gupta
2020-09-07 15:43     ` Burakov, Anatoly

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:

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

  git send-email \
    --in-reply-to=e58baac48f6bbe14e2ccba10e68eeace@mail.gmail.com \
    --to=vikas.gupta@broadcom.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=vikram.prakash@broadcom.com \


* 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).