From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: <anatoly.burakov@intel.com>
Cc: <dev@dpdk.org>, <thomas@monjalon.net>
Subject: [dpdk-dev] [PATCH] eal: fslmc bus need vfio enabled for non PCI case as well
Date: Thu, 13 Jul 2017 17:18:50 +0530 [thread overview]
Message-ID: <1499946530-29581-1-git-send-email-hemant.agrawal@nxp.com> (raw)
In case no_pci is configured, fslmc bus will still need the
the vfio to be enabled.
Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
lib/librte_eal/linuxapp/eal/eal.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/lib/librte_eal/linuxapp/eal/eal.c b/lib/librte_eal/linuxapp/eal/eal.c
index 7c78f2d..0484396 100644
--- a/lib/librte_eal/linuxapp/eal/eal.c
+++ b/lib/librte_eal/linuxapp/eal/eal.c
@@ -722,6 +722,13 @@ static int rte_eal_vfio_setup(void)
vfio_enabled |= pci_vfio_is_enabled();
}
+#ifdef RTE_LIBRTE_FSLMC_BUS
+ if (!vfio_enabled) {
+ if (!vfio_enable("vfio_fsl_mc"))
+ vfio_enabled = 1;
+ }
+#endif
+
if (vfio_enabled) {
/* if we are primary process, create a thread to communicate with
--
2.7.4
next reply other threads:[~2017-07-13 11:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 11:48 Hemant Agrawal [this message]
2017-10-05 23:41 ` Thomas Monjalon
2017-10-06 16:22 ` Hemant Agrawal
2017-10-06 17:08 ` Thomas Monjalon
2017-10-07 11:22 ` Hemant Agrawal
2017-10-07 11:20 ` [dpdk-dev] [PATCH v2] eal: enable vfio independent of no PCI flag Hemant Agrawal
2017-10-07 11:37 ` Thomas Monjalon
2017-10-10 13:46 ` Hemant Agrawal
2017-10-10 16:27 ` Thomas Monjalon
2017-10-11 6:42 ` [dpdk-dev] [PATCH v3] eal: enable vfio independent of PCI bus Hemant Agrawal
2017-10-23 6:33 ` [dpdk-dev] FW: " Hemant Agrawal
2017-10-23 11:00 ` Burakov, Anatoly
2017-10-23 11:47 ` [dpdk-dev] " Burakov, Anatoly
2017-10-23 22:32 ` 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=1499946530-29581-1-git-send-email-hemant.agrawal@nxp.com \
--to=hemant.agrawal@nxp.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).