From: <pbhagavatula@marvell.com>
To: <jerinj@marvell.com>, Sunil Kumar Kori <skori@marvell.com>,
Ray Kinsella <mdr@ashroe.eu>, Neil Horman <nhorman@tuxdriver.com>
Cc: <dev@dpdk.org>, Pavan Nikhilesh <pbhagavatula@marvell.com>
Subject: [dpdk-dev] [PATCH 2/2] trace: add size_t as a generic trace point
Date: Wed, 26 Aug 2020 04:54:09 +0530 [thread overview]
Message-ID: <20200825232410.975-2-pbhagavatula@marvell.com> (raw)
In-Reply-To: <20200825232410.975-1-pbhagavatula@marvell.com>
From: Pavan Nikhilesh <pbhagavatula@marvell.com>
Add size_t as a generic trace point. Also, update
test_generic_trace_point() to validate size_t emitter.
Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
---
app/test/test_trace.c | 1 +
lib/librte_eal/common/eal_common_trace_points.c | 2 ++
lib/librte_eal/include/rte_eal_trace.h | 6 ++++++
lib/librte_eal/rte_eal_version.map | 3 +++
4 files changed, 12 insertions(+)
diff --git a/app/test/test_trace.c b/app/test/test_trace.c
index ddcf416b2..0f9df83c4 100644
--- a/app/test/test_trace.c
+++ b/app/test/test_trace.c
@@ -166,6 +166,7 @@ test_generic_trace_points(void)
rte_eal_trace_generic_double(20000.5000004);
rte_eal_trace_generic_ptr(&tmp);
rte_eal_trace_generic_str("my string");
+ rte_eal_trace_generic_size_t(sizeof(void *));
RTE_EAL_TRACE_GENERIC_FUNC;
return TEST_SUCCESS;
diff --git a/lib/librte_eal/common/eal_common_trace_points.c b/lib/librte_eal/common/eal_common_trace_points.c
index 292ec91be..0b0b25461 100644
--- a/lib/librte_eal/common/eal_common_trace_points.c
+++ b/lib/librte_eal/common/eal_common_trace_points.c
@@ -36,6 +36,8 @@ RTE_TRACE_POINT_REGISTER(rte_eal_trace_generic_ptr,
lib.eal.generic.ptr)
RTE_TRACE_POINT_REGISTER(rte_eal_trace_generic_str,
lib.eal.generic.string)
+RTE_TRACE_POINT_REGISTER(rte_eal_trace_generic_size_t,
+ lib.eal.generic.size_t)
RTE_TRACE_POINT_REGISTER(rte_eal_trace_generic_func,
lib.eal.generic.func)
diff --git a/lib/librte_eal/include/rte_eal_trace.h b/lib/librte_eal/include/rte_eal_trace.h
index 6b1a813c7..19df549d2 100644
--- a/lib/librte_eal/include/rte_eal_trace.h
+++ b/lib/librte_eal/include/rte_eal_trace.h
@@ -129,6 +129,12 @@ RTE_TRACE_POINT(
rte_trace_point_emit_string(str);
)
+RTE_TRACE_POINT(
+ rte_eal_trace_generic_size_t,
+ RTE_TRACE_POINT_ARGS(size_t sz),
+ rte_trace_point_emit_size_t(sz);
+)
+
RTE_TRACE_POINT(
rte_eal_trace_generic_func,
RTE_TRACE_POINT_ARGS(const char *func),
diff --git a/lib/librte_eal/rte_eal_version.map b/lib/librte_eal/rte_eal_version.map
index 0b18e2ef8..4ccfa593f 100644
--- a/lib/librte_eal/rte_eal_version.map
+++ b/lib/librte_eal/rte_eal_version.map
@@ -397,6 +397,9 @@ EXPERIMENTAL {
rte_mp_disable;
rte_thread_register;
rte_thread_unregister;
+
+ #added in 20.11
+ __rte_eal_trace_generic_size_t;
};
INTERNAL {
--
2.17.1
next prev parent reply other threads:[~2020-08-25 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 23:24 [dpdk-dev] [PATCH 1/2] trace: fix size_t field emitter pbhagavatula
2020-08-25 23:24 ` pbhagavatula [this message]
2020-08-30 7:36 ` [dpdk-dev] [PATCH 2/2] trace: add size_t as a generic trace point Sunil Kumar Kori
2020-10-07 12:41 ` Thomas Monjalon
2020-08-30 7:35 ` [dpdk-dev] [PATCH 1/2] trace: fix size_t field emitter Sunil Kumar Kori
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=20200825232410.975-2-pbhagavatula@marvell.com \
--to=pbhagavatula@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.com \
--cc=skori@marvell.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).