From: David Marchand <david.marchand@redhat.com>
To: Takeshi T Yoshimura <TYOS@jp.ibm.com>
Cc: dev <dev@dpdk.org>, David Christensen <drc@linux.vnet.ibm.com>
Subject: Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc
Date: Thu, 1 Aug 2019 09:15:21 +0200 [thread overview]
Message-ID: <CAJFAV8xc2txr2uPAy=db8_Xr9-6ia8JJtNP2fWv+vnW2ZpeEEg@mail.gmail.com> (raw)
In-Reply-To: <OFFCB5A2C6.AF7A3BFF-ON00258449.001DA2FD-00258449.001DC9E5@notes.na.collabserv.com>
On Thu, Aug 1, 2019 at 7:25 AM Takeshi T Yoshimura <TYOS@jp.ibm.com> wrote:
> Okay. I should have set the --log-level=lib.*:debug. Here is the log.
>
> Starting SPDK v19.10-pre / DPDK 19.08.0-rc3 initialization...
> [ DPDK EAL parameters: identify --no-shconf -c 0x1 -n 1 -m 0 --log-level=lib.eal:6 --log-level=lib.cryptodev:5 --log-level=user1:6 --log-level=lib.*:debug --base-virtaddr=0x200000000000 --match-allocations --file-prefix=spdk_pid159692 ]
[snip]
> EAL: No shared files mode enabled, IPC will be disabled
> EAL: No shared files mode enabled, IPC is disabled
> EAL: VFIO PCI modules not loaded
EAL thinks that vfio kmod is not loaded at this point.
> EAL: Bus pci wants IOVA as 'DC'
We see no log here for the devices that are used later.
- Are the (below) devices bound to vfio-pci or any other kmod at this
point of the init?
- Is the spdk_nvme driver loaded at this point?
- I suppose forcing --iova-mode=pa resolves the issue, but can you confirm this?
> EAL: Buses did not request a specific IOVA mode.
> EAL: IOMMU is available, selecting IOVA as VA mode.
> EAL: Module /sys/module/rte_kni not found! error 2 (No such file or directory)
> EAL: Selected IOVA mode 'VA'
[snip]
> EAL: PCI device 0000:01:00.0 on NUMA socket 0
> EAL: probe driver: 144d:a822 spdk_nvme
> EAL: Expecting 'PA' IOVA mode but current mode is 'VA', not initializing
> EAL: Requested device 0000:01:00.0 cannot be used
> EAL: PCI device 0003:01:00.0 on NUMA socket 0
> EAL: probe driver: 144d:a822 spdk_nvme
> EAL: Expecting 'PA' IOVA mode but current mode is 'VA', not initializing
> EAL: Requested device 0003:01:00.0 cannot be used
> EAL: PCI device 0030:01:00.0 on NUMA socket 8
> EAL: probe driver: 144d:a822 spdk_nvme
> EAL: Expecting 'PA' IOVA mode but current mode is 'VA', not initializing
> EAL: Requested device 0030:01:00.0 cannot be used
> No NVMe controllers found.
--
David Marchand
next prev parent reply other threads:[~2019-08-01 7:15 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
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 [this message]
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='CAJFAV8xc2txr2uPAy=db8_Xr9-6ia8JJtNP2fWv+vnW2ZpeEEg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=TYOS@jp.ibm.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.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).