From: talshn@mellanox.com
To: dev@dpdk.org
Cc: thomas@monjalon.net, pallavi.kadam@intel.com,
dmitry.kozliuk@gmail.com, david.marchand@redhat.com,
grive@u256.net, ranjit.menon@intel.com,
navasile@linux.microsoft.com, harini.ramakrishnan@microsoft.com,
ocardona@microsoft.com, anatoly.burakov@intel.com,
Tal Shnaiderman <talshn@mellanox.com>
Subject: [dpdk-dev] [PATCH v2 2/2] bus/vdev: build on Windows
Date: Tue, 7 Jul 2020 11:48:23 +0300 [thread overview]
Message-ID: <20200707084823.28160-3-talshn@mellanox.com> (raw)
In-Reply-To: <20200707084823.28160-1-talshn@mellanox.com>
From: Tal Shnaiderman <talshn@mellanox.com>
current support will build vdev with empty MP functions
currently unsupported for Windows.
Signed-off-by: Tal Shnaiderman <talshn@mellanox.com>
---
drivers/bus/vdev/meson.build | 6 ------
lib/librte_eal/rte_eal_exports.def | 5 +++++
2 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/bus/vdev/meson.build b/drivers/bus/vdev/meson.build
index 3a662b1075..967d54e4f8 100644
--- a/drivers/bus/vdev/meson.build
+++ b/drivers/bus/vdev/meson.build
@@ -1,12 +1,6 @@
# SPDX-License-Identifier: BSD-3-Clause
# Copyright(c) 2017 Intel Corporation
-if is_windows
- build = false
- reason = 'not supported on Windows'
- subdir_done()
-endif
-
sources = files('vdev.c',
'vdev_params.c')
install_headers('rte_bus_vdev.h')
diff --git a/lib/librte_eal/rte_eal_exports.def b/lib/librte_eal/rte_eal_exports.def
index 69204a92c6..f54ed74a58 100644
--- a/lib/librte_eal/rte_eal_exports.def
+++ b/lib/librte_eal/rte_eal_exports.def
@@ -11,6 +11,7 @@ EXPORTS
rte_calloc_socket
rte_bus_register
rte_dev_is_probed
+ rte_devargs_insert
rte_devargs_next
rte_devargs_remove
rte_eal_get_configuration
@@ -29,6 +30,9 @@ EXPORTS
rte_eal_using_phys_addrs
rte_free
rte_hexdump
+ rte_log_register
+ rte_log_register_type_and_pick_level
+ rte_log_set_level
rte_malloc
rte_malloc_dump_stats
rte_malloc_get_socket_stats
@@ -62,6 +66,7 @@ EXPORTS
rte_memzone_walk
rte_strerror
rte_strsplit
+ rte_sys_gettid
rte_vfio_container_dma_map
rte_vfio_container_dma_unmap
rte_vlog
--
2.16.1.windows.4
next prev parent reply other threads:[~2020-07-07 8:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 14:56 [dpdk-dev] [PATCH 0/2] Windows bus/vdev support talshn
2020-06-24 14:56 ` [dpdk-dev] [PATCH 1/2] eal/windows: Add needed calls to detect vdev PMD talshn
2020-07-06 23:38 ` Thomas Monjalon
2020-07-07 0:43 ` Narcisa Ana Maria Vasile
2020-07-07 8:04 ` Tal Shnaiderman
2020-07-07 8:39 ` Dmitry Kozlyuk
2020-07-07 18:04 ` Ranjit Menon
2020-07-07 8:48 ` [dpdk-dev] [PATCH v2 0/2] Windows bus/vdev support talshn
2020-07-07 8:48 ` [dpdk-dev] [PATCH v2 1/2] eal/windows: add needed calls to detect vdev PMD talshn
2020-07-16 20:54 ` Narcisa Ana Maria Vasile
2020-07-07 8:48 ` talshn [this message]
2020-07-16 20:53 ` [dpdk-dev] [PATCH v2 2/2] bus/vdev: build on Windows Narcisa Ana Maria Vasile
2020-07-20 19:18 ` [dpdk-dev] [PATCH v2 0/2] Windows bus/vdev support Kadam, Pallavi
2020-09-09 12:41 ` Thomas Monjalon
2020-06-24 14:56 ` [dpdk-dev] [PATCH 2/2] bus/vdev: Windows support talshn
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=20200707084823.28160-3-talshn@mellanox.com \
--to=talshn@mellanox.com \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=grive@u256.net \
--cc=harini.ramakrishnan@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=ocardona@microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--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).