From: Shahaf Shuler <shahafs@mellanox.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org, anatoly.burakov@intel.com
Subject: [dpdk-dev] [PATCH] eal: fix compilation without VFIO
Date: Thu, 12 Apr 2018 16:34:22 +0300 [thread overview]
Message-ID: <20180412133422.104155-1-shahafs@mellanox.com> (raw)
a compilation error occurred when compiling with CONFIG_RTE_EAL_VFIO=n
== Build lib/librte_eal/linuxapp/eal
CC eal_vfio.o
/download/dpdk/lib/librte_eal/linuxapp/eal/eal_vfio.c:1535:1: error: no
previous prototype for 'rte_vfio_dma_map' [-Werror=missing-prototypes]
rte_vfio_dma_map(uint64_t __rte_unused vaddr, __rte_unused uint64_t
iova,
^
/download/dpdk/lib/librte_eal/linuxapp/eal/eal_vfio.c:1542:1: error: no
previous prototype for 'rte_vfio_dma_unmap' [-Werror=missing-prototypes]
rte_vfio_dma_unmap(uint64_t __rte_unused vaddr, uint64_t __rte_unused
iova,
^
As there is no use for those dummy functions without VFIO removing them
completely.
Fixes: 73a639085938 ("vfio: allow to map other memory regions")
Cc: anatoly.burakov@intel.com
Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
---
lib/librte_eal/linuxapp/eal/eal_vfio.c | 16 ----------------
1 file changed, 16 deletions(-)
diff --git a/lib/librte_eal/linuxapp/eal/eal_vfio.c b/lib/librte_eal/linuxapp/eal/eal_vfio.c
index 589d7d4787..4163bd4e08 100644
--- a/lib/librte_eal/linuxapp/eal/eal_vfio.c
+++ b/lib/librte_eal/linuxapp/eal/eal_vfio.c
@@ -1529,20 +1529,4 @@ rte_vfio_noiommu_is_enabled(void)
return c == 'Y';
}
-#else
-
-int __rte_experimental
-rte_vfio_dma_map(uint64_t __rte_unused vaddr, __rte_unused uint64_t iova,
- __rte_unused uint64_t len)
-{
- return -1;
-}
-
-int __rte_experimental
-rte_vfio_dma_unmap(uint64_t __rte_unused vaddr, uint64_t __rte_unused iova,
- __rte_unused uint64_t len)
-{
- return -1;
-}
-
#endif
--
2.12.0
next reply other threads:[~2018-04-12 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 13:34 Shahaf Shuler [this message]
2018-04-12 14:13 ` Burakov, Anatoly
2018-04-12 23:39 ` Thomas Monjalon
2018-04-13 9:11 ` Burakov, Anatoly
2018-04-13 13:08 ` Thomas Monjalon
2018-04-13 13:37 ` Burakov, Anatoly
2018-04-13 13:58 ` Thomas Monjalon
2018-04-16 5:50 ` Shahaf Shuler
2018-04-16 10:09 ` 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:
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=20180412133422.104155-1-shahafs@mellanox.com \
--to=shahafs@mellanox.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).