In many cases, it's enough to simply let the application know that the call to initialize DPDK has failed. A complete halt can then be decided by the application based on error returned (and the app could even attempt a possible re-attempt after some corrective action by the user or application).
Aaron Conole (24): eal: CPU init will no longer panic eal: return error instead of panic for cpu init eal: No panic on hugepages info init eal: do not panic on failed hugepage query eal: failure to parse args returns error eal-common: introduce a way to query cpu support eal: Signal error when CPU isn't supported eal: do not panic on memzone initialization fails eal: set errno when exiting for already called eal: Do not panic on log failures eal: Do not panic on pci-probe eal: do not panic on vfio failure eal: do not panic on memory init eal: do not panic on tailq init eal: do not panic on alarm init eal: convert timer_init not to call panic eal: change the private pipe call to reflect errno eal: Do not panic on interrupt thread init eal: do not error if plugins fail to init eal_pci: Continue probing even on failures eal: do not panic on failed PCI probe eal_common_dev: continue initializing vdevs eal: do not panic (or abort) if vdev init fails eal: do not panic when bus probe fails lib/librte_eal/common/eal_common_cpuflags.c | 13 ++- lib/librte_eal/common/eal_common_dev.c | 5 +- lib/librte_eal/common/eal_common_lcore.c | 7 +- lib/librte_eal/common/eal_common_pci.c | 15 ++- lib/librte_eal/common/eal_common_tailqs.c | 4 +- .../common/include/generic/rte_cpuflags.h | 9 ++ lib/librte_eal/linuxapp/eal/eal.c | 121 +++++++++++++++------ lib/librte_eal/linuxapp/eal/eal_hugepage_info.c | 6 +- lib/librte_eal/linuxapp/eal/eal_interrupts.c | 5 +- 9 files changed, 135 insertions(+), 50 deletions(-) -- 2.7.4
