From: David Marchand <david.marchand@redhat.com>
To: Takeshi Yoshimura <tyos@jp.ibm.com>,
David Christensen <drc@linux.vnet.ibm.com>
Cc: "Burakov, Anatoly" <anatoly.burakov@intel.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] bus/pci: always check IOMMU capabilities
Date: Fri, 2 Aug 2019 12:20:38 +0200 [thread overview]
Message-ID: <CAJFAV8xM9EHU6bYYs+=1PJ=xrS4ECXPrygKwmkXWt4AfXMY-4w@mail.gmail.com> (raw)
In-Reply-To: <1564740872-27225-1-git-send-email-david.marchand@redhat.com>
On Fri, Aug 2, 2019 at 12:14 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> IOMMU capabilities won't change and must be checked even if no PCI device
> seem to be supported yet when EAL initialised.
>
> This is to accommodate with SPDK that registers its drivers after
> rte_eal_init(), especially on PPC platform where the IOMMU does not
> support VA.
David, Takeshi,
Can you test your setups with (only) this patch?
This should address both of your issues.
>
> Fixes: 703458e19c16 ("bus/pci: consider only usable devices for IOVA mode")
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> drivers/bus/pci/bsd/pci.c | 6 ++++++
> drivers/bus/pci/linux/pci.c | 25 ++++++-------------------
> drivers/bus/pci/pci_common.c | 16 +++++++++++++++-
> drivers/bus/pci/private.h | 5 ++++-
> 4 files changed, 31 insertions(+), 21 deletions(-)
>
[snip]
> diff --git a/drivers/bus/pci/pci_common.c b/drivers/bus/pci/pci_common.c
> index 9794552..8d1d6ab 100644
> --- a/drivers/bus/pci/pci_common.c
> +++ b/drivers/bus/pci/pci_common.c
[snip]
> @@ -643,7 +651,13 @@ rte_pci_get_iommu_class(void)
> devices_want_va = true;
> }
> }
> - if (devices_want_va && !devices_want_pa) {
> + if (iommu_no_va == 1) {
> + iova_mode = RTE_IOVA_PA;
> + if (devices_want_va) {
> + RTE_LOG(WARNING, EAL, "Some devices want 'VA' but because IOMMU does not support 'VA'.\n");
Note to self, s/but because/but/
> + RTE_LOG(WARNING, EAL, "The devices that want 'VA' won't initialize.\n");
> + }
> + } else if (devices_want_va && !devices_want_pa) {
> iova_mode = RTE_IOVA_VA;
> } else if (devices_want_pa && !devices_want_va) {
> iova_mode = RTE_IOVA_PA;
--
David Marchand
next prev parent reply other threads:[~2019-08-02 10:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 10:14 David Marchand
2019-08-02 10:20 ` David Marchand [this message]
2019-08-02 17:13 ` David Christensen
2019-08-02 17:10 ` David Christensen
2019-08-03 18:22 ` Jerin Jacob Kollanukkaran
2019-08-05 3:57 ` Takeshi T Yoshimura
2019-08-05 6:16 ` David Marchand
2019-08-05 6:23 ` [dpdk-dev] [PATCH v2] " David Marchand
2019-08-05 10:09 ` 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='CAJFAV8xM9EHU6bYYs+=1PJ=xrS4ECXPrygKwmkXWt4AfXMY-4w@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=tyos@jp.ibm.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).