From: Stephen Hemminger <stephen@networkplumber.org>
To: Nandini Rangaswamy <nandini.rangaswamy@broadcom.com>
Cc: users@dpdk.org, Long Li <longli@microsoft.com>
Subject: Re: Regarding net_netvsc driver registration with VMBUS
Date: Wed, 17 Jul 2024 10:08:48 -0700 [thread overview]
Message-ID: <20240717100848.403fc652@hermes.local> (raw)
In-Reply-To: <CAAkQrK9bar4yppnnKMFfth2p8R5Vj6LbqwoekCqmHN1O2_D9Sg@mail.gmail.com>
On Wed, 17 Jul 2024 09:17:07 -0700
Nandini Rangaswamy <nandini.rangaswamy@broadcom.com> wrote:
> Hi Stephen,
> I am using dpdk 22.11 . I used testpmd with the same and it worked . Also
> , I compared testpmd logs with that if the app and did not find difference
> except that netvsc driver not being probed. Can you give inputs on when rte
> vmbus registration is invoked ? I can see netvsc declaring the macro that
> expands to function definition but could not trace where it is being called
Please test with 22.11.5. The vmbus handling is done as part of rte_eal_init().
Part of the problem might be your use of block/allow lists (formerly known as
blacklist/whitelist) options. If you don't list the vmbus device in the allow
list it would be ignored.
PS: I no longer work at Microsoft, and Long Li handles the driver now.
It is expensive and difficult for me to do any netvsc tests.
prev parent reply other threads:[~2024-07-17 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 14:29 Nandini Rangaswamy
2024-07-17 15:11 ` Stephen Hemminger
2024-07-17 15:46 ` Nandini Rangaswamy
2024-07-17 16:03 ` Stephen Hemminger
2024-07-17 16:17 ` Nandini Rangaswamy
2024-07-17 17:08 ` Stephen Hemminger [this message]
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=20240717100848.403fc652@hermes.local \
--to=stephen@networkplumber.org \
--cc=longli@microsoft.com \
--cc=nandini.rangaswamy@broadcom.com \
--cc=users@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).