From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Subject: [PATCH v6 0/4] allow pmdinfo to be inserted and parsed using MSVC
Date: Tue, 10 Jun 2025 12:09:43 +0200 [thread overview]
Message-ID: <20250610100947.421877-1-david.marchand@redhat.com> (raw)
This is a rework of Andre v5, trying to hide the ugly details in a
driver only macro not exposed publicly.
--
David Marchand
Changes since v5:
- moved details in dev_driver.h,
- renamed RTE_INCLUDE as RTE_PMD_EXPORT_SYMBOL,
Andre Muezerie (3):
dev: export driver information with MSVC
buildtools: embed driver information with MSVC
usertools: enable pmdinfo with MSVC
David Marchand (1):
dev: hide driver export macros
buildtools/gen-pmdinfo-cfile.py | 25 +++++++--
buildtools/meson.build | 2 +
buildtools/pmdinfogen.py | 11 ++--
drivers/bus/auxiliary/bus_auxiliary_driver.h | 2 +-
drivers/bus/cdx/bus_cdx_driver.h | 5 +-
drivers/bus/dpaa/bus_dpaa_driver.h | 2 +-
drivers/bus/fslmc/bus_fslmc_driver.h | 4 +-
drivers/bus/ifpga/bus_ifpga_driver.h | 2 +-
drivers/bus/pci/bus_pci_driver.h | 2 +-
drivers/bus/platform/bus_platform_driver.h | 2 +-
drivers/bus/uacce/bus_uacce_driver.h | 2 +-
drivers/bus/vdev/bus_vdev_driver.h | 2 +-
drivers/bus/vmbus/bus_vmbus_driver.h | 2 +-
drivers/common/mlx5/mlx5_common.c | 2 +-
drivers/common/mlx5/mlx5_common_pci.c | 2 +-
drivers/common/nitrox/nitrox_device.c | 1 +
drivers/compress/mlx5/mlx5_compress.c | 2 +-
drivers/crypto/mlx5/mlx5_crypto.c | 2 +-
drivers/event/octeontx/ssovf_evdev.c | 1 +
drivers/net/mlx4/mlx4.c | 2 +-
drivers/net/mlx5/mlx5.c | 2 +-
drivers/net/virtio/virtio_pci_ethdev.c | 2 +-
drivers/regex/mlx5/mlx5_regex.c | 2 +-
drivers/vdpa/mlx5/mlx5_vdpa.c | 2 +-
lib/eal/common/eal_common_options.c | 2 +-
lib/eal/include/dev_driver.h | 45 +++++++++++++++++
lib/eal/include/rte_dev.h | 41 ---------------
usertools/dpdk-pmdinfo.py | 53 ++++++++++++++++----
28 files changed, 140 insertions(+), 84 deletions(-)
--
2.49.0
next reply other threads:[~2025-06-10 10:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 10:09 David Marchand [this message]
2025-06-10 10:09 ` [PATCH v6 1/4] dev: hide driver export macros David Marchand
2025-06-10 10:09 ` [PATCH v6 2/4] dev: export driver information with MSVC David Marchand
2025-06-10 12:13 ` David Marchand
2025-06-10 10:09 ` [PATCH v6 3/4] buildtools: embed " David Marchand
2025-06-10 10:09 ` [PATCH v6 4/4] usertools: enable pmdinfo " David Marchand
2025-06-10 10:17 ` Robin Jarry
2025-06-11 9:45 ` [PATCH v7 0/5] allow pmdinfo to be inserted and parsed using MSVC David Marchand
2025-06-11 9:45 ` [PATCH v7 1/5] dev: hide driver export macros David Marchand
2025-06-11 13:24 ` Andre Muezerie
2025-06-11 9:45 ` [PATCH v7 2/5] dev: rename pmdinfo internal symbols David Marchand
2025-06-11 13:26 ` Andre Muezerie
2025-06-11 9:45 ` [PATCH v7 3/5] dev: export driver information with MSVC David Marchand
2025-06-11 13:27 ` Andre Muezerie
2025-06-11 9:45 ` [PATCH v7 4/5] buildtools: embed " David Marchand
2025-06-11 13:28 ` Andre Muezerie
2025-06-11 9:45 ` [PATCH v7 5/5] usertools: enable pmdinfo " David Marchand
2025-06-12 13:23 ` [PATCH v7 0/5] allow pmdinfo to be inserted and parsed using MSVC 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=20250610100947.421877-1-david.marchand@redhat.com \
--to=david.marchand@redhat.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).