[dpdk-dev] [PATCH v6 00/26] linux/eal: Remove most causes of panic on init
Thomas Monjalon
thomas.monjalon at 6wind.com
Wed Mar 8 22:58:27 CET 2017
Hi,
Thanks for the work.
I think it needs to be completed to have the same behaviour on bsdapp.
As a another version is required, I add some small comments about
the formatting.
I think you should use the form "do not panic on <step>" for most
of the commits.
Some commits may be squashed (see below):
2017-02-28 13:52, Aaron Conole:
> Aaron Conole (26):
> eal: cpu init will no longer panic
> eal: return error instead of panic for cpu init
squashed?
> eal: do not panic on hugepage info init
> eal: do not panic on failed hugepage query
squashed?
> eal: do not panic if parsing args returns error
> eal-common: introduce a way to query cpu support
> eal: do not panic when CPU isn't supported
squashed?
> 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
It is not really the probe here
> 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
squashed?
> eal_common_dev: continue initializing vdevs
> eal: do not panic (or abort) if vdev init fails
squashed?
> eal: do not panic when bus probe fails
> eal: do not panic on failed bus scan
> rte_eal_init: add info about various error codes
More information about the dev
mailing list