From: Jakub Kicinski <kuba@kernel.org>
To: Deli Zhang <deli.zhang21th@gmail.com>
Cc: michael.chan@broadcom.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bnxt_en: Add parameter disable_vf_bind
Date: Wed, 25 Jun 2025 14:13:49 -0700 [thread overview]
Message-ID: <20250625141349.5315d6cc@kernel.org> (raw)
In-Reply-To: <20250625053005.79845-1-deli.zhang21th@gmail.com>
On Wed, 25 Jun 2025 13:30:05 +0800 Deli Zhang wrote:
> In virtualization, VF is usually not bound by native drivers, instead
> should be passthrough to VM. Most PF and VF drivers provide separate
> names, e.g. "igb" and "igbvf", so that the hypervisor can control
> whether to use VF devices locally. The "bnxt_en" driver is a special
> case, it can drive both PF and VF devices, so here add a parameter
> "disable_vf_bind" to allow users to control.
sriov_drivers_autoprobe
prev parent reply other threads:[~2025-06-25 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 5:30 [PATCH] bnxt_en: Add parameter disable_vf_bind Deli Zhang
2025-06-25 13:42 ` Pavan Chebbi
2025-06-25 21:13 ` Jakub Kicinski [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=20250625141349.5315d6cc@kernel.org \
--to=kuba@kernel.org \
--cc=deli.zhang21th@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.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).