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: <CALs4sv3BmZLTvodCJL-W0MQSAwMgkqfPbxgNt2oDgkgsR+DVbA@mail.gmail.com>
Date: Wed, 25 Jun 2025 19:12:34 +0530
From: Pavan Chebbi <pavan.chebbi@...adcom.com>
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, Jun 25, 2025 at 11:01 AM Deli Zhang <deli.zhang21th@...il.com> 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.

You can always unbind the driver using the sysfs interface, right?
Besides, module params are not acceptable.

Download attachment "smime.p7s" of type "application/pkcs7-signature" (4196 bytes)