From: Andrew Lunn <andrew@lunn.ch>
To: Shannon Nelson <shannon.nelson@amd.com>
Cc: jgg@nvidia.com, andrew.gospodarek@broadcom.com,
aron.silverton@oracle.com, dan.j.williams@intel.com,
daniel.vetter@ffwll.ch, dave.jiang@intel.com, dsahern@kernel.org,
gospo@broadcom.com, hch@infradead.org, itayavr@nvidia.com,
jiri@nvidia.com, Jonathan.Cameron@huawei.com, kuba@kernel.org,
lbloch@nvidia.com, leonro@nvidia.com, saeedm@nvidia.com,
linux-cxl@vger.kernel.org, linux-rdma@vger.kernel.org,
netdev@vger.kernel.org, brett.creeley@amd.com
Subject: Re: [RFC PATCH fwctl 0/5] pds_fwctl: fwctl for AMD/Pensando core devices
Date: Wed, 12 Feb 2025 14:40:45 +0100 [thread overview]
Message-ID: <7a9d5e34-4a1c-4e91-9a25-805052ffd73e@lunn.ch> (raw)
In-Reply-To: <20250211234854.52277-1-shannon.nelson@amd.com>
> existing function-specific tools. For example, these are things that make
> the Eth PCI device appear on the PCI bus
That sounds like a common operation which many vendors will need? So
why use fwctl for this? The whole point of fwctl is things which are
highly vendor specific and not networking.
Isn't this even generic for any sort of SR-IOV? Wouldn't you need the
same sort of operation for a GPU, or anything with a pool of resources
which can be mapped to VFs?
If you really want to use this as you key selling point, you need to
clearly explain why is this highly vendor specific and cannot be
generalised.
Andrew
next prev parent reply other threads:[~2025-02-12 13:41 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 23:48 [RFC PATCH fwctl 0/5] pds_fwctl: fwctl for AMD/Pensando core devices Shannon Nelson
2025-02-11 23:48 ` [RFC PATCH fwctl 1/5] pds_core: specify auxiliary_device to be created Shannon Nelson
2025-02-12 11:57 ` Jonathan Cameron
2025-02-13 22:44 ` Nelson, Shannon
2025-02-11 23:48 ` [RFC PATCH fwctl 2/5] pds_core: add new fwctl auxilary_device Shannon Nelson
2025-02-12 12:02 ` Jonathan Cameron
2025-02-13 22:48 ` Nelson, Shannon
2025-02-12 12:03 ` Jonathan Cameron
2025-02-13 22:49 ` Nelson, Shannon
2025-02-18 19:28 ` Leon Romanovsky
2025-02-18 20:00 ` Nelson, Shannon
2025-02-19 8:24 ` Leon Romanovsky
2025-02-20 23:20 ` Nelson, Shannon
2025-02-22 18:26 ` Leon Romanovsky
2025-02-11 23:48 ` [RFC PATCH fwctl 3/5] pds_fwctl: initial driver framework Shannon Nelson
2025-02-12 12:22 ` Jonathan Cameron
2025-02-13 23:06 ` Nelson, Shannon
2025-02-14 0:55 ` Jason Gunthorpe
2025-02-12 23:26 ` Dave Jiang
2025-02-13 23:31 ` Nelson, Shannon
2025-02-18 19:51 ` Leon Romanovsky
2025-02-18 22:19 ` Nelson, Shannon
2025-02-19 8:25 ` Leon Romanovsky
2025-02-20 23:27 ` Nelson, Shannon
2025-02-22 18:29 ` Leon Romanovsky
2025-02-11 23:48 ` [RFC PATCH fwctl 4/5] pds_fwctl: add rpc and query support Shannon Nelson
2025-02-12 12:47 ` Jonathan Cameron
2025-02-13 23:13 ` Nelson, Shannon
2025-02-13 1:02 ` Dave Jiang
2025-02-13 23:34 ` Nelson, Shannon
2025-02-11 23:48 ` [RFC PATCH fwctl 5/5] pds_fwctl: add Documentation entries Shannon Nelson
2025-02-12 12:51 ` Jonathan Cameron
2025-02-12 13:13 ` Jason Gunthorpe
2025-02-12 14:23 ` Leon Romanovsky
2025-02-13 23:18 ` Nelson, Shannon
2025-02-12 13:40 ` Andrew Lunn [this message]
2025-02-12 14:43 ` [RFC PATCH fwctl 0/5] pds_fwctl: fwctl for AMD/Pensando core devices Jason Gunthorpe
2025-02-12 16:19 ` Andrew Lunn
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=7a9d5e34-4a1c-4e91-9a25-805052ffd73e@lunn.ch \
--to=andrew@lunn.ch \
--cc=Jonathan.Cameron@huawei.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=aron.silverton@oracle.com \
--cc=brett.creeley@amd.com \
--cc=dan.j.williams@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dave.jiang@intel.com \
--cc=dsahern@kernel.org \
--cc=gospo@broadcom.com \
--cc=hch@infradead.org \
--cc=itayavr@nvidia.com \
--cc=jgg@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=lbloch@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=shannon.nelson@amd.com \
/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