From: Ankur Dwivedi <adwivedi@marvell.com>
To: <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <david.marchand@redhat.com>,
<ferruh.yigit@amd.com>, <jerinj@marvell.com>,
Ankur Dwivedi <adwivedi@marvell.com>
Subject: [PATCH v3 0/5] remove internal tracepoints from version map
Date: Wed, 15 Feb 2023 15:12:23 +0530 [thread overview]
Message-ID: <20230215094228.1452656-1-adwivedi@marvell.com> (raw)
In-Reply-To: <20230210103446.1126999-1-adwivedi@marvell.com>
The internal tracepoints of a library are not needed to be exported in
version.map file, as they will not be called from outside the library.
This patch removes the internal tracepoints from version.map for mempool,
cryptodev, eal, ethdev and eventdev library.
v3:
- Updated the trace document in patch (3/5).
- Removed internal trace file from meson.build in ethdev and eventdev
library, in patches (4/5) and (5/5).
- Added acked by from Jerin for series.
v2:
- Removed the internal tracepoint header files from meson.build.
- Updated the trace document in
"eal: remove internal tracepoints from version map"
- Added acked by from Ferruh for
"ethdev: remove internal tracepoints from version map"
Ankur Dwivedi (5):
mempool: remove internal tracepoints from version map
cryptodev: remove internal tracepoints from version map
eal: remove internal tracepoints from version map
ethdev: remove internal tracepoints from version map
eventdev: remove internal tracepoints from version map
doc/guides/prog_guide/trace_lib.rst | 3 +-
...te_cryptodev_trace.h => cryptodev_trace.h} | 6 +-
lib/cryptodev/cryptodev_trace_points.c | 2 +-
lib/cryptodev/meson.build | 1 -
lib/cryptodev/rte_cryptodev.c | 2 +-
lib/cryptodev/version.map | 62 ------
lib/eal/common/eal_common_launch.c | 2 +-
lib/eal/common/eal_common_memzone.c | 2 +-
lib/eal/common/eal_common_thread.c | 2 +-
lib/eal/common/eal_common_trace_points.c | 2 +
lib/eal/common/rte_malloc.c | 2 +-
lib/eal/freebsd/eal_alarm.c | 2 +-
lib/eal/freebsd/eal_interrupts.c | 2 +-
lib/eal/include/eal_trace_internal.h | 182 ++++++++++++++++++
lib/eal/include/rte_eal_trace.h | 158 ---------------
lib/eal/linux/eal_alarm.c | 2 +-
lib/eal/linux/eal_interrupts.c | 2 +-
lib/eal/version.map | 15 --
lib/eal/windows/eal_alarm.c | 3 +-
lib/ethdev/ethdev_trace.h | 6 +-
lib/ethdev/meson.build | 1 -
lib/ethdev/version.map | 6 -
lib/eventdev/eventdev_trace.h | 6 +-
lib/eventdev/meson.build | 1 -
lib/eventdev/version.map | 30 ---
.../{rte_mempool_trace.h => mempool_trace.h} | 6 +-
lib/mempool/mempool_trace_points.c | 2 +-
lib/mempool/meson.build | 1 -
lib/mempool/rte_mempool.c | 2 +-
lib/mempool/rte_mempool_ops.c | 2 +-
lib/mempool/version.map | 14 --
31 files changed, 212 insertions(+), 317 deletions(-)
rename lib/cryptodev/{rte_cryptodev_trace.h => cryptodev_trace.h} (99%)
create mode 100644 lib/eal/include/eal_trace_internal.h
rename lib/mempool/{rte_mempool_trace.h => mempool_trace.h} (98%)
--
2.25.1
next prev parent reply other threads:[~2023-02-15 9:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 13:30 [PATCH v1 " Ankur Dwivedi
2023-02-09 13:30 ` [PATCH v1 1/5] mempool: " Ankur Dwivedi
2023-02-09 14:23 ` David Marchand
2023-02-10 5:32 ` [EXT] " Ankur Dwivedi
2023-02-10 5:44 ` Jerin Jacob
2023-02-10 7:00 ` [EXT] " Ankur Dwivedi
2023-02-10 7:06 ` Jerin Jacob
2023-02-10 14:24 ` David Marchand
2023-02-10 15:32 ` Jerin Jacob
2023-02-14 11:37 ` Ankur Dwivedi
2023-02-20 14:18 ` David Marchand
2023-02-09 13:30 ` [PATCH v1 2/5] cryptodev: " Ankur Dwivedi
2023-02-09 13:30 ` [PATCH v1 3/5] eal: " Ankur Dwivedi
2023-02-09 13:30 ` [PATCH v1 4/5] ethdev: " Ankur Dwivedi
2023-02-09 14:13 ` Ferruh Yigit
2023-02-09 13:30 ` [PATCH v1 5/5] eventdev: " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 0/5] " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 1/5] mempool: " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 2/5] cryptodev: " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 3/5] eal: " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 4/5] ethdev: " Ankur Dwivedi
2023-02-10 14:19 ` David Marchand
2023-02-13 8:14 ` [EXT] " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 5/5] eventdev: " Ankur Dwivedi
2023-02-10 13:08 ` Jerin Jacob
2023-02-15 9:42 ` Ankur Dwivedi [this message]
2023-02-15 9:42 ` [PATCH v3 1/5] mempool: " Ankur Dwivedi
2023-02-15 9:42 ` [PATCH v3 2/5] cryptodev: " Ankur Dwivedi
2023-02-15 9:42 ` [PATCH v3 3/5] eal: " Ankur Dwivedi
2023-02-15 9:42 ` [PATCH v3 4/5] ethdev: " Ankur Dwivedi
2023-02-15 9:42 ` [PATCH v3 5/5] eventdev: " Ankur Dwivedi
2023-02-20 14:39 ` [PATCH v3 0/5] " Thomas Monjalon
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=20230215094228.1452656-1-adwivedi@marvell.com \
--to=adwivedi@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jerinj@marvell.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).