All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: [PATCH 1/3] eal: make rte_cpu_get_intrinsics_support stable
Date: Wed,  4 Sep 2024 11:08:44 -0700	[thread overview]
Message-ID: <20240904180954.104473-2-stephen@networkplumber.org> (raw)
In-Reply-To: <20240904180954.104473-1-stephen@networkplumber.org>

This API was added in 20.11, after four years it should be stable.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 lib/eal/include/generic/rte_cpuflags.h | 4 ----
 lib/eal/version.map                    | 2 +-
 2 files changed, 1 insertion(+), 5 deletions(-)

diff --git a/lib/eal/include/generic/rte_cpuflags.h b/lib/eal/include/generic/rte_cpuflags.h
index d35551e931..fe48d62518 100644
--- a/lib/eal/include/generic/rte_cpuflags.h
+++ b/lib/eal/include/generic/rte_cpuflags.h
@@ -29,15 +29,11 @@ struct rte_cpu_intrinsics {
 };
 
 /**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
  * Check CPU support for various intrinsics at runtime.
  *
  * @param intrinsics
  *     Pointer to a structure to be filled.
  */
-__rte_experimental
 void
 rte_cpu_get_intrinsics_support(struct rte_cpu_intrinsics *intrinsics);
 
diff --git a/lib/eal/version.map b/lib/eal/version.map
index e3ff412683..cabe881bfe 100644
--- a/lib/eal/version.map
+++ b/lib/eal/version.map
@@ -23,6 +23,7 @@ DPDK_25 {
 	rte_class_unregister;
 	rte_cpu_get_flag_enabled;
 	rte_cpu_get_flag_name;
+	rte_cpu_get_intrinsics_support; # WINDOWS_NO_EXPORT
 	rte_cpu_is_supported; # WINDOWS_NO_EXPORT
 	rte_cycles_vmware_tsc_map; # WINDOWS_NO_EXPORT
 	rte_delay_us;
@@ -384,7 +385,6 @@ EXPERIMENTAL {
 
 	# added in 20.11
 	__rte_eal_trace_generic_size_t; # WINDOWS_NO_EXPORT
-	rte_cpu_get_intrinsics_support; # WINDOWS_NO_EXPORT
 
 	# added in 23.03
 	rte_lcore_register_usage_cb;
-- 
2.45.2


  reply	other threads:[~2024-09-04 18:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 18:08 [PATCH 0/3] eal: mark API's as stable Stephen Hemminger
2024-09-04 18:08 ` Stephen Hemminger [this message]
2024-09-04 18:08 ` [PATCH 2/3] eal: mark rte_lcore_register_usage_cb stable Stephen Hemminger
2024-10-04 12:56   ` Robin Jarry
2024-09-04 18:08 ` [PATCH 3/3] eal: mark rte_memzone_max_get/set stable Stephen Hemminger
2024-09-05  6:07 ` [PATCH 0/3] eal: mark API's as stable Morten Brørup
2024-09-05  7:58 ` David Marchand
2024-09-05  8:55   ` Morten Brørup
2024-09-05  9:03     ` David Marchand
2024-09-05  9:44       ` Morten Brørup
2024-09-05 14:01         ` Jerin Jacob
2024-09-05 14:18           ` Morten Brørup
2024-09-08 23:58             ` Stephen Hemminger
2024-09-06  8:54           ` Ferruh Yigit
2024-09-06 10:04             ` Morten Brørup
2024-09-06 14:12               ` Ferruh Yigit
2024-09-06 14:42                 ` Morten Brørup
2024-09-09  4:48                   ` Jerin Jacob
2024-09-06  9:34   ` Ferruh Yigit
2024-09-06  9:48     ` David Marchand
2024-09-06 11:00       ` Ferruh Yigit
2024-09-06 13:11     ` Jerin Jacob
2024-09-06 14:03       ` Ferruh Yigit
2024-09-09  4:46         ` Jerin Jacob
2024-10-30  9:10 ` David Marchand

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=20240904180954.104473-2-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=roretzla@linux.microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.