From: Jakub Kicinski <kuba@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Dave Jiang <dave.jiang@intel.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Dan Williams <dan.j.williams@intel.com>,
Shannon Nelson <shannon.nelson@amd.com>,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Please pull fwctl subsystem changes
Date: Wed, 26 Mar 2025 10:13:12 -0700 [thread overview]
Message-ID: <20250326101312.7557b3d1@kernel.org> (raw)
In-Reply-To: <Z+F2tcBM1LJpTDF9@nvidia.com>
On Mon, 24 Mar 2025 12:13:57 -0300 Jason Gunthorpe wrote:
> fwctl is a new subsystem intended to bring some common rules and order to
> the growing pattern of exposing a secure FW interface directly to
> userspace. Unlike existing places like RDMA/DRM/VFIO/uacce that are
> exposing a device for datapath operations fwctl is focused on debugging,
> configuration and provisioning of the device. It will not have the
> necessary features like interrupt delivery to support a datapath.
>
> This concept is similar to the long standing practice in the "HW" RAID
> space of having a device specific misc device to manage the RAID
> controller FW. fwctl generalizes this notion of a companion debug and
> management interface that goes along with a dataplane implemented in an
> appropriate subsystem.
This breaks netdev's long standing policy against exposing proprietary
interfaces (proprietary user space <> proprietary FW). I've been asking
all this time for the interface to be disabled if the device is used
purely as a netdev. Hopefully retaining the benefits of community
standards for majority of users who only use netdev. This has not been
done.
next prev parent reply other threads:[~2025-03-26 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 15:13 [GIT PULL] Please pull fwctl subsystem changes Jason Gunthorpe
2025-03-26 17:13 ` Jakub Kicinski [this message]
2025-03-29 18:24 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-04-17 12:36 [GIT PULL] Please pull FWCTL " Jason Gunthorpe
2025-04-17 18:57 ` pr-tracker-bot
2025-10-01 19:35 Jason Gunthorpe
2025-10-04 1:41 ` pr-tracker-bot
2026-04-16 14:11 Jason Gunthorpe
2026-04-17 4:28 ` pr-tracker-bot
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=20250326101312.7557b3d1@kernel.org \
--to=kuba@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=jgg@nvidia.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=shannon.nelson@amd.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.