From: Chas Williams <3chas3@gmail.com>
To: dev@dpdk.org
Cc: skhare@vmware.com, Chas Williams <3chas3@gmail.com>,
Chas Williams <chas3@att.com>
Subject: [dpdk-dev] [PATCH] vfio: try physical address if virtual address fails
Date: Fri, 24 Nov 2017 18:57:18 -0500 [thread overview]
Message-ID: <20171124235718.6064-1-3chas3@gmail.com> (raw)
Some machines appear to have buggy DMAR mappings. A typical mapping
error looks like:
DMAR: intel_iommu_map: iommu width (39) is not sufficient for the mapped address (7fc4fa800000)
DMAR: intel_iommu_map: iommu width (39) is not sufficient for the mapped address (7fc4fa800000)
DMAR: intel_iommu_map: iommu width (39) is not sufficient for the mapped address (7fc4fa800000)
DMAR: intel_iommu_map: iommu width (39) is not sufficient for the mapped address (7fc4fa800000)
To work around this, attempt to do a physical address mapping if the
virtual address mapping fails.
Fixes: e85a919286d2 ("vfio: honor IOVA mode before mapping")
Signed-off-by: Chas Williams <chas3@att.com>
---
lib/librte_eal/linuxapp/eal/eal_vfio.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/lib/librte_eal/linuxapp/eal/eal_vfio.c b/lib/librte_eal/linuxapp/eal/eal_vfio.c
index 58f0123..6250676 100644
--- a/lib/librte_eal/linuxapp/eal/eal_vfio.c
+++ b/lib/librte_eal/linuxapp/eal/eal_vfio.c
@@ -35,6 +35,7 @@
#include <fcntl.h>
#include <unistd.h>
#include <sys/ioctl.h>
+#include <stdbool.h>
#include <rte_log.h>
#include <rte_memory.h>
@@ -702,6 +703,7 @@ vfio_type1_dma_map(int vfio_container_fd)
/* map all DPDK segments for DMA. use 1:1 PA to IOVA mapping */
for (i = 0; i < RTE_MAX_MEMSEG; i++) {
struct vfio_iommu_type1_dma_map dma_map;
+ int retried = false;
if (ms[i].addr == NULL)
break;
@@ -716,9 +718,15 @@ vfio_type1_dma_map(int vfio_container_fd)
dma_map.iova = ms[i].iova;
dma_map.flags = VFIO_DMA_MAP_FLAG_READ | VFIO_DMA_MAP_FLAG_WRITE;
+retry:
ret = ioctl(vfio_container_fd, VFIO_IOMMU_MAP_DMA, &dma_map);
if (ret) {
+ if (!retried && rte_eal_iova_mode() == RTE_IOVA_VA) {
+ dma_map.iova = ms[i].iova;
+ retried = true;
+ goto retry;
+ }
RTE_LOG(ERR, EAL, " cannot set up DMA remapping, "
"error %i (%s)\n", errno,
strerror(errno));
--
2.9.5
next reply other threads:[~2017-11-24 23:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 23:57 Chas Williams [this message]
2017-11-27 9:30 ` Zhang, Qi Z
2017-11-27 12:58 ` Chas Williams
2017-11-30 2:03 ` Chas Williams
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=20171124235718.6064-1-3chas3@gmail.com \
--to=3chas3@gmail.com \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=skhare@vmware.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).