From: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
To: <mb@smartsharesystems.com>, <david.marchand@redhat.com>,
<ktraynor@redhat.com>, <thomas@monjalon.net>,
<konstantin.ananyev@huawei.com>, <konstantin.v.ananyev@yandex.ru>,
<bruce.richardson@intel.com>, <maxime.coquelin@redhat.com>,
<aconole@redhat.com>, <ferruh.yigit@amd.com>
Cc: <dev@dpdk.org>, <ciara.power@intel.com>, <stable@dpdk.org>
Subject: [PATCH] examples/l3fwd-power: fix telemetry command registration
Date: Mon, 6 Oct 2025 10:10:58 +0000 [thread overview]
Message-ID: <20251006101058.191495-1-sivaprasad.tummala@amd.com> (raw)
Telemetry command registration fails if the command name contains
characters other than alphanumeric, underscore (_), and forward
slash (/).
The l3fwd-power example previously used "/l3fwd-power/stats"
as telemetry command, which includes a hyphen (-) and causes
registration failure.
This patch fixes the issue by replacing the hyphen with an
underscore, changing the command to "/l3fwd_power/stats"
Fixes: a35919a1139b ("examples/l3fwd-power: use new telemetry")
Cc: ciara.power@intel.com
Cc: stable@dpdk.org
Signed-off-by: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
---
examples/l3fwd-power/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/examples/l3fwd-power/main.c b/examples/l3fwd-power/main.c
index e27b8531b5..f9ce9e6698 100644
--- a/examples/l3fwd-power/main.c
+++ b/examples/l3fwd-power/main.c
@@ -2910,7 +2910,7 @@ main(int argc, char **argv)
rte_spinlock_init(&stats[lcore_id].telemetry_lock);
}
rte_timer_init(&telemetry_timer);
- rte_telemetry_register_cmd("/l3fwd-power/stats",
+ rte_telemetry_register_cmd("/l3fwd_power/stats",
handle_app_stats,
"Returns global power stats. Parameters: None");
rte_eal_mp_remote_launch(main_telemetry_loop, NULL,
--
2.43.0
reply other threads:[~2025-10-06 10:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251006101058.191495-1-sivaprasad.tummala@amd.com \
--to=sivaprasad.tummala@amd.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.power@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=konstantin.ananyev@huawei.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mb@smartsharesystems.com \
--cc=stable@dpdk.org \
--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).