From: Arnon Warshavsky <arnon@qwilt.com>
To: thomas@monjalon.net, anatoly.burakov@intel.com,
wenzhuo.lu@intel.com, declan.doherty@intel.com,
jerin.jacob@caviumnetworks.com, bruce.richardson@intel.com,
ferruh.yigit@intel.com
Cc: dev@dpdk.org, arnon@qwilt.com
Subject: [dpdk-dev] [PATCH v2 00/13] eal: replace calls to rte_panic and refrain from new instances
Date: Thu, 5 Apr 2018 01:01:32 +0300 [thread overview]
Message-ID: <1522879294-8803-1-git-send-email-arnon@qwilt.com> (raw)
The purpose of this patch series is to cleanup the library code
from paths that end up aborting the process,
and move to checking error values, in order to allow the running process
perform an orderly teardown or other mitigation of the event.
This patch modifies the majority of rte_panic calls
under lib and drivers, and replaces them with a log message
and an error return code according to context,
that can be propagated up the call stack.
- Focus was given to the dpdk initialization path
- Some of the panic calls within drivers were left in place where
the call is from within an interrupt or calls that are
on the data path,where there is no simple applicative
route to propagate the error to temination.
These should be handled by the driver maintainers.
- In order to avoid breaking ABI where panic was called from public
void functions, a panic state variable was introduced so that
it can be queried after calling these void functions.
This tool place for a single function call.
- local void functions with no api were changed to retrun a value
where needed
- No change took place in example and test files
- No change took place for debug assertions calling panic
- A new function was added to devtools/checkpatches.sh
in order to prevent new additions of calls to rte_panic
under lib and drivers.
Keep calm and don't panic
---
v2:
- reformat error messages so that literal string are in the same line
- fix typo in commit message
- add new return code to doxigen of rte_memzone_free()
Arnon Warshavsky (13):
crypto: replace rte_panic instances in crypto driver
bond: replace rte_panic instances in bonding driver
e1000: replace rte_panic instances in e1000 driver
ixgbe: replace rte_panic instances in ixgbe driver
eal: replace rte_panic instances in eventdev
kni: replace rte_panic instances in kni
e1000: replace rte_panic instances in e1000 driver
eal: replace rte_panic instances in hugepage_info
eal: replace rte_panic instances in common_memzone
eal: replace rte_panic instances in interrupts thread
eal: replace rte_panic instances in ethdev
eal: replace rte_panic instances in init sequence
devtools: prevent new instances of rte_panic and rte_exit
devtools/checkpatches.sh | 94 ++++++++++++++++-
drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c | 8 +-
drivers/crypto/dpaa_sec/dpaa_sec.c | 8 +-
drivers/net/bonding/rte_eth_bond_8023ad.c | 30 ++++--
drivers/net/bonding/rte_eth_bond_8023ad_private.h | 2 +-
drivers/net/bonding/rte_eth_bond_api.c | 20 ++--
drivers/net/bonding/rte_eth_bond_pmd.c | 10 +-
drivers/net/bonding/rte_eth_bond_private.h | 2 +-
drivers/net/e1000/e1000_ethdev.h | 2 +-
drivers/net/e1000/igb_ethdev.c | 3 +-
drivers/net/e1000/igb_pf.c | 15 +--
drivers/net/ixgbe/ixgbe_ethdev.c | 3 +-
drivers/net/ixgbe/ixgbe_ethdev.h | 2 +-
drivers/net/ixgbe/ixgbe_pf.c | 13 ++-
lib/librte_eal/bsdapp/eal/eal.c | 87 +++++++++++-----
lib/librte_eal/bsdapp/eal/eal_thread.c | 65 +++++++++---
lib/librte_eal/common/eal_common_launch.c | 21 ++++
lib/librte_eal/common/eal_common_memzone.c | 3 +-
lib/librte_eal/common/include/rte_debug.h | 12 +++
lib/librte_eal/common/include/rte_memzone.h | 1 +
lib/librte_eal/common/rte_malloc.c | 7 +-
lib/librte_eal/linuxapp/eal/eal.c | 121 +++++++++++++++-------
lib/librte_eal/linuxapp/eal/eal_hugepage_info.c | 21 ++--
lib/librte_eal/linuxapp/eal/eal_interrupts.c | 27 +++--
lib/librte_eal/linuxapp/eal/eal_thread.c | 65 +++++++++---
lib/librte_ether/rte_ethdev.c | 36 +++++--
lib/librte_eventdev/rte_eventdev_pmd_pci.h | 8 +-
lib/librte_eventdev/rte_eventdev_pmd_vdev.h | 8 +-
lib/librte_kni/rte_kni.c | 18 ++--
lib/librte_kni/rte_kni_fifo.h | 11 +-
30 files changed, 540 insertions(+), 183 deletions(-)
--
1.8.3.1
next reply other threads:[~2018-04-04 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 22:01 Arnon Warshavsky [this message]
2018-04-04 22:01 ` [dpdk-dev] [PATCH v2 09/13] eal: replace rte_panic instances in common_memzone Arnon Warshavsky
2018-04-04 22:01 ` [dpdk-dev] [PATCH v2 01/13] crypto: replace rte_panic instances in crypto driver Arnon Warshavsky
2018-04-13 9:16 ` [dpdk-dev] [PATCH v2 00/13] eal: replace calls to rte_panic and refrain from new instances Burakov, Anatoly
2018-04-13 18:21 ` Arnon Warshavsky
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=1522879294-8803-1-git-send-email-arnon@qwilt.com \
--to=arnon@qwilt.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=thomas@monjalon.net \
--cc=wenzhuo.lu@intel.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).