10/03/2014 23:29, Daniel Kan :
> virtio-pmd has the same pattern. I wonder if vmxnet3-pmd just blindly copied
> the same paradigm.
>
> 473 static struct eth_driver rte_virtio_pmd = {
> 474 {
> 475 .name = "rte_virtio_pmd",
> 476 .id_table = pci_id_virtio_map,
> 477 #ifdef RTE_E
virtio-pmd has the same pattern. I wonder if vmxnet3-pmd just blindly copied
the same paradigm.
lib/librte_pmd_virtio/virtio_ethdev.c
473 static struct eth_driver rte_virtio_pmd = {
474 {
475 .name = "rte_virtio_pmd",
476 .id_table = pci_id_virtio_map,
477 #ifdef RTE_EAL_UNBI
Upon further trace, I know what caused it. The uio hardware resources were
never memory mapped when RTE_EAL_UNBIND_PORTS is not enabled. Specifically,
pci_dev->mem_resource[] is not mapped. This explains why setting
CONFIG_RTE_EAL_UNBIND_PORTS=y fixes the problem.
lib/librte_pmd_vmxnet3/vmxne
I also got the segfault. Setting CONFIG_RTE_EAL_UNBIND_PORTS=y is not ideal
because it would also unbind my VMNET3 management interface.
Does anyone know why the crash is happening? According to the stacktrace,
hw_addrX is 0x0 during eth_vmxnet3_dev_init.
I?m running on ubuntu 12.04LTS on ESXi
4 matches
Mail list logo
