linux-kernel - Re: [PATCH] bnxt_en: Add parameter disable_vf

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250625141349.5315d6cc@kernel.org>
Date: Wed, 25 Jun 2025 14:13:49 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Deli Zhang <deli.zhang21th@...il.com>
Cc: michael.chan@...adcom.com, netdev@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] bnxt_en: Add parameter disable_vf_bind

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