From: Vincent Li <vincent.mc.li@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] virtio still blindly take over virtio device managed by kernel
Date: Wed, 4 May 2016 09:21:03 -0700 [thread overview]
Message-ID: <CAK3+h2xx3pe9XsRO-TD8yyRZoGUOV8qhj3YUdkntcSvQ72FHEA@mail.gmail.com> (raw)
Hi,
I am running the dpdk git repo which already had commit ac5e1d838dc
(virtio: skip error when probing kernel managed device), but in my
test, it seems still taking control of the kernel managed virtio
device and segmentation fault, here is the example:
# ./tools/dpdk_nic_bind.py --status
Network devices using DPDK-compatible driver
============================================
0000:00:07.0 'Virtio network device' drv=igb_uio unused=
0000:00:08.0 'Virtio network device' drv=igb_uio unused=
Network devices using kernel driver
===================================
0000:00:03.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
#./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -- -i
EAL: Detected 4 lcore(s)
EAL: Probing VFIO support...
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using
unreliable clock cycles !
EAL: PCI device 0000:00:03.0 on NUMA socket -1
EAL: probe driver: 1af4:1000 rte_virtio_pmd
PMD: vtpci_init(): trying with legacy virtio pci.
Segmentation fault (core dumped)
if I blacklist 0000:00:03.0 from testpmd, testpmd works:
# ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -b 0000:00:03.0 -- -i
EAL: Detected 4 lcore(s)
EAL: Probing VFIO support...
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using
unreliable clock cycles !
EAL: PCI device 0000:00:03.0 on NUMA socket -1
EAL: PCI device 0000:00:07.0 on NUMA socket -1
EAL: probe driver: 1af4:1000 rte_virtio_pmd
PMD: virtio_read_caps(): no modern virtio pci device found.
PMD: vtpci_init(): trying with legacy virtio pci.
EAL: PCI device 0000:00:08.0 on NUMA socket -1
EAL: probe driver: 1af4:1000 rte_virtio_pmd
PMD: virtio_read_caps(): no modern virtio pci device found.
PMD: vtpci_init(): trying with legacy virtio pci.
Interactive-mode selected
Configuring Port 0 (socket 0)
rte_eth_dev_config_restore: port 0: MAC address array not supported
Port 0: 52:54:00:EA:6E:3E
Configuring Port 1 (socket 0)
rte_eth_dev_config_restore: port 1: MAC address array not supported
Port 1: 52:54:00:24:06:DB
Checking link statuses...
Port 0 Link Up - speed 10000 Mbps - full-duplex
Port 1 Link Up - speed 10000 Mbps - full-duplex
Done
testpmd>
next reply other threads:[~2016-05-04 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 16:21 Vincent Li [this message]
2016-05-04 16:48 ` Xie, Huawei
2016-05-06 8:30 ` Xie, Huawei
2016-05-06 20:08 ` Vincent Li
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=CAK3+h2xx3pe9XsRO-TD8yyRZoGUOV8qhj3YUdkntcSvQ72FHEA@mail.gmail.com \
--to=vincent.mc.li@gmail.com \
--cc=dev@dpdk.org \
/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).