From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Subject: [PATCH v1 2/2] doc: add deprecation notice for vDPA driver API
Date: Wed, 19 Nov 2025 10:35:38 +0000 [thread overview]
Message-ID: <a816720dff092ddc02ff9fcf734a353505fbcd6d.1763548356.git.anatoly.burakov@intel.com> (raw)
In-Reply-To: <cover.1763548356.git.anatoly.burakov@intel.com>
Currently, vDPA driver API is partly built around VFIO group API, which
will be removed in a future release and replaced with a device container
assignment API. Make this know in deprecation notice.
Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
---
doc/guides/rel_notes/deprecation.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 55d3837150..b63dc8b715 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -151,3 +151,6 @@ Deprecation Notices
* eal: The entire VFIO API (``rte_vfio_*``) will be made internal only, and will only be available to EAL and drivers.
Group-based API (``rte_vfio_*_group_*``) will be removed and replaced with unified container device assignment API.
This change will be made in 26.11 release.
+
+* vdpa: vDPA driver API will no longer offer ``get_vfio_group_fd`` as part of its internal API.
+ All drivers will be adjusted to use the new unified VFIO container device assignment API.
--
2.47.3
next prev parent reply other threads:[~2025-11-19 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 10:35 [PATCH v1 0/2] Deprecation notices for VFIO Anatoly Burakov
2025-11-19 10:35 ` [PATCH v1 1/2] doc: add deprecation notice for VFIO API Anatoly Burakov
2025-11-19 10:35 ` Anatoly Burakov [this message]
2025-11-19 10:43 ` [PATCH v1 0/2] Deprecation notices for VFIO Bruce Richardson
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=a816720dff092ddc02ff9fcf734a353505fbcd6d.1763548356.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.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).