From: Hemant <hemant.agrawal@nxp.com>
To: eric zhang <eric.zhang@windriver.com>,
anatoly.burakov@intel.com, bruce.richardson@intel.com
Cc: dev@dpdk.org, Allain.Legacy@windriver.com, Matt.Peters@windriver.com
Subject: Re: [dpdk-dev] [PATCH] eal: force IOVA mode to physical
Date: Thu, 30 Aug 2018 11:43:57 +0530 [thread overview]
Message-ID: <7d4fd31b-925a-4020-0301-0121c6bf96cc@nxp.com> (raw)
In-Reply-To: <1535558289-10336-1-git-send-email-eric.zhang@windriver.com>
On 8/29/2018 9:28 PM, eric zhang wrote:
> This patch adds a configuration option to force the IOVA mode to
> physical address (PA). There exists virtual devices that are not
> directly attached to the PCI bus, and therefore the auto detection
> of the IOVA mode based on probing the PCI bus and IOMMU configuration
> may not report the required addressing mode. Having the configuration
> option permits the mode to be explicitly configured in this scenario.
>
> Signed-off-by: eric zhang <eric.zhang@windriver.com>
> ---
> lib/librte_eal/linuxapp/eal/eal.c | 7 +++++++
you will also need the same in bsdapp/eal
> 1 file changed, 7 insertions(+)
>
> diff --git a/lib/librte_eal/linuxapp/eal/eal.c b/lib/librte_eal/linuxapp/eal/eal.c
> index e0b5ae1..bee4aed 100644
> --- a/lib/librte_eal/linuxapp/eal/eal.c
> +++ b/lib/librte_eal/linuxapp/eal/eal.c
> @@ -805,6 +805,7 @@ static void rte_eal_init_alert(const char *msg)
> return -1;
> }
>
> +#ifndef RTE_EAL_IOVA_MODE_PA
Add the default option as 'n' in config/common_base
> /* autodetect the iova mapping mode (default is iova_pa) */
> rte_eal_get_configuration()->iova_mode = rte_bus_get_iommu_class();
>
> @@ -816,6 +817,12 @@ static void rte_eal_init_alert(const char *msg)
> "Some devices want IOVA as VA but PA will be used because.. "
> "KNI module inserted\n");
> }
> +#else
> + /* Force iova mapping mode to be physical address */
> + rte_eal_get_configuration()->iova_mode = RTE_IOVA_PA;
> + RTE_LOG(WARNING, EAL,
> + "Force the iova mapping mode to be physical address\n");
> +#endif
>
> if (internal_config.no_hugetlbfs == 0 &&
> internal_config.process_type != RTE_PROC_SECONDARY &&
next prev parent reply other threads:[~2018-08-30 6:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 15:58 eric zhang
2018-08-30 6:13 ` Hemant [this message]
2018-08-30 9:09 ` Burakov, Anatoly
2018-08-30 9:43 ` Gaëtan Rivet
2018-08-30 12:13 ` Hemant
2018-08-30 12:59 ` santosh
2018-08-30 13:56 ` Legacy, Allain
2018-08-30 13:58 ` santosh
2018-09-05 3:40 ` Eric Zhang
2018-09-06 7:34 ` Jerin Jacob
2018-09-07 9:26 ` Burakov, Anatoly
2018-09-07 20:13 ` Eric Zhang
2018-09-11 17:21 ` Eric Zhang
2018-09-17 8:32 ` Stojaczyk, Dariusz
2018-09-17 19:04 ` Eric Zhang
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=7d4fd31b-925a-4020-0301-0121c6bf96cc@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=Allain.Legacy@windriver.com \
--cc=Matt.Peters@windriver.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=eric.zhang@windriver.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).