From: David Marchand <david.marchand@redhat.com>
To: David Christensen <drc@linux.vnet.ibm.com>
Cc: Takeshi T Yoshimura <TYOS@jp.ibm.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>, dev <dev@dpdk.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc
Date: Wed, 31 Jul 2019 21:32:42 +0200 [thread overview]
Message-ID: <CAJFAV8y4wDWc+CoSvqMYDpTY-c7OV7-3Mj_2tjc+VXiy0W_m4Q@mail.gmail.com> (raw)
In-Reply-To: <5bb4f727-b07e-5f52-de0e-f5552cb6420a@linux.vnet.ibm.com>
On Wed, Jul 31, 2019 at 9:23 PM David Christensen
<drc@linux.vnet.ibm.com> wrote:
>
> On 7/31/19 3:58 AM, David Marchand wrote:
> > --log-level lib.*:debug
>
> Here's the output from my Power 9 system running 19.08-RC2 (I'm not
> using VFIO since I have an MLX5 adapter).
>
> sudo -E LD_LIBRARY_PATH=/home/davec/src/dpdk/build/lib
> /home/davec/src/dpdk/build/app/testpmd --log-level lib.\*:debug -w
> 0000:01:00.0 -w 0000:01:00.1 -l 4,8-79 -n 4 -- --rxq=32 --rxd=1024
> --txq=32 --txd=4096 --nb-cores=64 -i -a --numa --forward-mode=rxonly
> EAL: Detected lcore 0 as core 0 on socket 0
> <snip> ...
> EAL: Detected lcore 159 as core 2140 on socket 8
> EAL: Support maximum 1536 logical core(s) by configuration.
> EAL: Detected 160 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Module /sys/module/vfio_pci not found! error 2 (No such file or
> directory)
> EAL: VFIO PCI modules not loaded
> EAL: DPAA Bus not present. Skipping.
> EAL: Bus pci wants IOVA as 'DC'
Ok, I think I understand now.
Can you try this hunk ?
diff --git a/drivers/bus/pci/pci_common.c b/drivers/bus/pci/pci_common.c
index 9794552..6d3b553 100644
--- a/drivers/bus/pci/pci_common.c
+++ b/drivers/bus/pci/pci_common.c
@@ -620,9 +620,6 @@ rte_pci_get_iommu_class(void)
FOREACH_DEVICE_ON_PCIBUS(dev) {
if (pci_ignore_device(dev))
continue;
- if (dev->kdrv == RTE_KDRV_UNKNOWN ||
- dev->kdrv == RTE_KDRV_NONE)
- continue;
FOREACH_DRIVER_ON_PCIBUS(drv) {
enum rte_iova_mode dev_iova_mode;
--
David Marchand
next prev parent reply other threads:[~2019-07-31 19:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 3:35 Takeshi Yoshimura
2019-07-31 9:10 ` Burakov, Anatoly
2019-07-31 9:29 ` David Marchand
2019-07-31 10:34 ` Takeshi T Yoshimura
2019-07-31 10:44 ` Takeshi T Yoshimura
2019-07-31 10:58 ` David Marchand
2019-07-31 19:23 ` David Christensen
2019-07-31 19:32 ` David Marchand [this message]
2019-07-31 21:20 ` David Christensen
2019-08-01 5:04 ` David Marchand
2019-07-31 19:44 ` David Marchand
2019-08-01 4:10 ` Takeshi T Yoshimura
2019-08-01 5:01 ` David Marchand
2019-08-01 5:25 ` Takeshi T Yoshimura
2019-08-01 7:15 ` David Marchand
2019-08-01 8:46 ` Takeshi T Yoshimura
2019-08-01 9:46 ` David Marchand
2019-08-02 8:09 ` Takeshi T Yoshimura
2019-08-02 8:22 ` David Marchand
2019-08-01 4:12 ` Takeshi T Yoshimura
2019-08-01 13:01 ` David Marchand
2019-08-02 8:50 ` 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=CAJFAV8y4wDWc+CoSvqMYDpTY-c7OV7-3Mj_2tjc+VXiy0W_m4Q@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=TYOS@jp.ibm.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=maxime.coquelin@redhat.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).