From: longli@linuxonhyperv.com
To: Stephen Hemminger <stephen@networkplumber.org>,
Wei Hu <weh@microsoft.com>
Cc: dev@dpdk.org, Long Li <longli@microsoft.com>
Subject: [patch v2 2/6] net/netvsc: introduce get_vmbus_device to get the vmbus device
Date: Mon, 10 Mar 2025 14:42:53 -0700 [thread overview]
Message-ID: <1741642977-14297-3-git-send-email-longli@linuxonhyperv.com> (raw)
In-Reply-To: <1741642977-14297-1-git-send-email-longli@linuxonhyperv.com>
From: Long Li <longli@microsoft.com>
Introduce a function get the vmbus device from hn_data. For secondary
process, the vmbus device is in eth_dev's private region.
Signed-off-by: Long Li <longli@microsoft.com>
---
drivers/net/netvsc/hn_nvs.c | 15 +++++++++++++++
drivers/net/netvsc/hn_nvs.h | 2 ++
2 files changed, 17 insertions(+)
diff --git a/drivers/net/netvsc/hn_nvs.c b/drivers/net/netvsc/hn_nvs.c
index 7db82af9f3..fd20e3d06d 100644
--- a/drivers/net/netvsc/hn_nvs.c
+++ b/drivers/net/netvsc/hn_nvs.c
@@ -44,6 +44,21 @@ static const uint32_t hn_nvs_version[] = {
NVS_VERSION_1
};
+struct rte_vmbus_device *get_vmbus_device(struct hn_data *hv)
+{
+ struct rte_vmbus_device *vmbus = hv->vmbus;
+
+ /* For secondary process, vmbus is in the eth_dev private */
+ if (rte_eal_process_type() == RTE_PROC_SECONDARY) {
+ struct rte_eth_dev *dev = &rte_eth_devices[hv->port_id];
+ struct hn_nvs_process_priv *process_priv = dev->process_private;
+
+ vmbus = process_priv->vmbus_dev;
+ }
+
+ return vmbus;
+}
+
static int hn_nvs_req_send(struct hn_data *hv,
void *req, uint32_t reqlen)
{
diff --git a/drivers/net/netvsc/hn_nvs.h b/drivers/net/netvsc/hn_nvs.h
index 3950749359..0d8fe27b65 100644
--- a/drivers/net/netvsc/hn_nvs.h
+++ b/drivers/net/netvsc/hn_nvs.h
@@ -221,6 +221,8 @@ void hn_nvs_handle_vfassoc(struct rte_eth_dev *dev,
const struct vmbus_chanpkt_hdr *hdr,
const void *data);
+struct rte_vmbus_device *get_vmbus_device(struct hn_data *hv);
+
static inline int
hn_nvs_send(struct vmbus_channel *chan, uint16_t flags,
void *nvs_msg, int nvs_msglen, uintptr_t sndc,
--
2.34.1
next prev parent reply other threads:[~2025-03-10 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 21:42 [patch v2 0/6] Support VMBUS channels without monitoring enabled longli
2025-03-10 21:42 ` [patch v2 1/6] net/netvsc: introduce private data for storing vmbus device for secondary process longli
2025-03-10 21:42 ` longli [this message]
2025-03-10 21:42 ` [patch v2 3/6] bus/vmbus: store UIO fd " longli
2025-03-10 21:42 ` [patch v2 4/6] bus/vmbus: support channels without monitoring enabled longli
2025-03-10 21:42 ` [patch v2 5/6] bus/vmbus: add rte_vmbus_device to all functions accessing vmbus longli
2025-03-10 21:42 ` [patch v2 6/6] bus/vmbus: set event for channel without monitoring support longli
2025-03-10 23:20 ` [patch v2 0/6] Support VMBUS channels without monitoring enabled Stephen Hemminger
2025-03-12 0:33 ` [EXTERNAL] " Long Li
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=1741642977-14297-3-git-send-email-longli@linuxonhyperv.com \
--to=longli@linuxonhyperv.com \
--cc=dev@dpdk.org \
--cc=longli@microsoft.com \
--cc=stephen@networkplumber.org \
--cc=weh@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 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).