From: talshn@mellanox.com
To: dev@dpdk.org
Cc: thomas@monjalon.net, pallavi.kadam@intel.com,
dmitry.kozliuk@gmail.com, david.marchand@redhat.com,
ranjit.menon@intel.com, navasile@linux.microsoft.com,
harini.ramakrishnan@microsoft.com, ocardona@microsoft.com,
bruce.richardson@intel.com, Tal Shnaiderman <talshn@mellanox.com>
Subject: [dpdk-dev] [PATCH 0/2] Support EAL debug functions on Windows
Date: Sun, 7 Jun 2020 12:35:27 +0300 [thread overview]
Message-ID: <20200607093529.15456-1-talshn@mellanox.com> (raw)
From: Tal Shnaiderman <talshn@mellanox.com>
This patchset adds support for the EAL debug function on Windows
by implementing backtracing in rte_dump_stack and
cleanup calls in rte_eal_cleanup.
Additionally, the functions rte_exit, __rte_panic
and rte_dump_registers were moved to a common file
to avoid code duplication.
Tal Shnaiderman (2):
eal: move OS common debug functions to single file
eal/windows: support debug calls
config/meson.build | 1 +
lib/librte_eal/common/eal_common_debug.c | 56 +++++++++++++++++++++++
lib/librte_eal/common/meson.build | 2 +
lib/librte_eal/freebsd/Makefile | 1 +
lib/librte_eal/freebsd/eal_debug.c | 49 --------------------
lib/librte_eal/linux/Makefile | 1 +
lib/librte_eal/linux/eal_debug.c | 49 --------------------
lib/librte_eal/windows/eal.c | 7 +++
lib/librte_eal/windows/eal_debug.c | 77 ++++++++++++++++++++++++++++----
9 files changed, 136 insertions(+), 107 deletions(-)
create mode 100644 lib/librte_eal/common/eal_common_debug.c
--
2.16.1.windows.4
next reply other threads:[~2020-06-07 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 9:35 talshn [this message]
2020-06-07 9:35 ` [dpdk-dev] [PATCH 1/2] eal: move OS common debug functions to single file talshn
2020-06-07 9:35 ` [dpdk-dev] [PATCH 2/2] eal/windows: support debug calls talshn
2020-06-08 0:31 ` Dmitry Kozlyuk
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=20200607093529.15456-1-talshn@mellanox.com \
--to=talshn@mellanox.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=harini.ramakrishnan@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=ocardona@microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=thomas@monjalon.net \
/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).