From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [PATCH 14/15] eal: mark rte_eal_vfio_get_token stable
Date: Wed, 9 Aug 2023 10:55:30 -0700 [thread overview]
Message-ID: <20230809175530.GD22800@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <20230809164312.308093-15-stephen@networkplumber.org>
On Wed, Aug 09, 2023 at 09:43:06AM -0700, Stephen Hemminger wrote:
> This API was added in 20.08 release.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
there is driver work going on for similar functionality to vfio on
windows. it's possible that this api could be exposed for windows but
in the current form may not be suitable.
*not blocking*
just wanted to make you aware, i don't have a firm enough schedule to
derail this process.
> lib/eal/include/rte_eal.h | 4 ----
> lib/eal/version.map | 4 +---
> 2 files changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/lib/eal/include/rte_eal.h b/lib/eal/include/rte_eal.h
> index 53c4a5519e61..aac57665e6c2 100644
> --- a/lib/eal/include/rte_eal.h
> +++ b/lib/eal/include/rte_eal.h
> @@ -412,16 +412,12 @@ int rte_eal_create_uio_dev(void);
> enum rte_intr_mode rte_eal_vfio_intr_mode(void);
>
> /**
> - * @warning
> - * @b EXPERIMENTAL: this API may change without prior notice
> - *
> * Copy the user-configured vfio VF token.
> *
> * @param vf_token
> * vfio VF token configured with the command line is copied
> * into this parameter, zero uuid by default.
> */
> -__rte_experimental
> void rte_eal_vfio_get_vf_token(rte_uuid_t vf_token);
>
> /**
> diff --git a/lib/eal/version.map b/lib/eal/version.map
> index 3b42d6e0e4c1..65435ae48696 100644
> --- a/lib/eal/version.map
> +++ b/lib/eal/version.map
> @@ -89,6 +89,7 @@ DPDK_24 {
> rte_eal_tailq_lookup;
> rte_eal_tailq_register;
> rte_eal_using_phys_addrs;
> + rte_eal_vfio_get_vf_token; # WINDOWS_NO_EXPORT
> rte_eal_vfio_intr_mode; # WINDOWS_NO_EXPORT
> rte_eal_wait_lcore;
> rte_epoll_ctl;
> @@ -396,9 +397,6 @@ EXPERIMENTAL {
> rte_trace_regexp; # WINDOWS_NO_EXPORT
> rte_trace_save; # WINDOWS_NO_EXPORT
>
> - # added in 20.08
> - rte_eal_vfio_get_vf_token; # WINDOWS_NO_EXPORT
> -
> # added in 20.11
> __rte_eal_trace_generic_size_t; # WINDOWS_NO_EXPORT
> rte_cpu_get_intrinsics_support; # WINDOWS_NO_EXPORT
> --
> 2.39.2
next prev parent reply other threads:[~2023-08-09 17:55 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 16:42 [PATCH 00/15] eal: mark older API's stable Stephen Hemminger
2023-08-09 16:42 ` [PATCH 01/15] eal: make bitops a stable API Stephen Hemminger
2023-08-09 17:58 ` Tyler Retzlaff
2023-08-09 20:07 ` Stephen Hemminger
2023-08-09 21:59 ` Tyler Retzlaff
2023-08-09 16:42 ` [PATCH 02/15] eal: mark rte_dev API's as stable Stephen Hemminger
2023-08-09 16:42 ` [PATCH 03/15] eal: make rte_class API's stable Stephen Hemminger
2023-08-09 16:42 ` [PATCH 04/15] eal: make rte_version_XXX " Stephen Hemminger
2023-08-10 8:24 ` Bruce Richardson
2023-08-09 16:42 ` [PATCH 05/15] eal: make rte_drand a stable API Stephen Hemminger
2023-08-09 16:42 ` [PATCH 06/15] eal: make rte_service_lcore_may_be_active stable Stephen Hemminger
2023-08-10 9:08 ` Van Haaren, Harry
2023-08-09 16:42 ` [PATCH 07/15] eal: make rte_devargs_reset stable Stephen Hemminger
2023-08-09 16:43 ` [PATCH 08/15] eal: make pflock API stable Stephen Hemminger
2023-08-09 16:43 ` [PATCH 09/15] eal: make seqcount and seqlock stable Stephen Hemminger
2023-08-09 19:47 ` Mattias Rönnblom
2023-08-09 16:43 ` [PATCH 10/15] eal: mark rte_intr_XXX API's as stable Stephen Hemminger
2023-08-09 16:43 ` [PATCH 11/15] eal: mark rte_atomic128_cmp_exchange " Stephen Hemminger
2023-08-09 17:50 ` Tyler Retzlaff
2023-08-09 16:43 ` [PATCH 12/15] eal: make most rte_thread API's stable Stephen Hemminger
2023-08-09 17:53 ` Tyler Retzlaff
2023-08-09 16:43 ` [PATCH 13/15] eal: mark rte_power " Stephen Hemminger
2023-08-09 16:43 ` [PATCH 14/15] eal: mark rte_eal_vfio_get_token stable Stephen Hemminger
2023-08-09 17:55 ` Tyler Retzlaff [this message]
2023-08-09 16:43 ` [PATCH 15/15] eal: mark rte_vect simd bandwidth API as stable Stephen Hemminger
2023-10-18 19:29 ` [PATCH 00/15] eal: mark older API's stable David Marchand
2023-10-20 21:41 ` [PATCH v2 00/14] eal: mark older API's as stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 01/14] eal: make bitops a stable API Stephen Hemminger
2023-10-23 2:31 ` Joyce Kong
2023-10-20 21:41 ` [PATCH v2 02/14] eal: mark rte_dev API's as stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 03/14] eal: make rte_class API's stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 04/14] eal: make rte_drand a stable API Stephen Hemminger
2023-10-23 16:12 ` Mattias Rönnblom
2023-10-20 21:41 ` [PATCH v2 05/14] eal: make rte_service_lcore_may_be_active stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 06/14] eal: make rte_devargs_reset stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 07/14] eal: make pflock API stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 08/14] eal: make seqcount and seqlock stable Stephen Hemminger
2023-10-23 16:14 ` Mattias Rönnblom
2023-10-20 21:41 ` [PATCH v2 09/14] eal: mark rte_intr_XXX API's as stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 10/14] eal: mark rte_atomic128_cmp_exchange " Stephen Hemminger
2023-10-23 3:00 ` Ruifeng Wang
2023-10-20 21:41 ` [PATCH v2 11/14] eal: mark rte_power API's stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 12/14] eal: mark rte_eal_vfio_get_token stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 13/14] eal: mark rte_vect simd bandwidth API as stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 14/14] eal: make rte_version API's stable Stephen Hemminger
2023-10-23 9:13 ` [PATCH v2 00/14] eal: mark older API's as stable Bruce Richardson
2023-11-14 13: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=20230809175530.GD22800@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=roretzla@linux.microsoft.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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).