From: "Nelson, Shannon" <shannon.nelson@amd.com>
To: Leon Romanovsky <leonro@nvidia.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, 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 3/5] pds_fwctl: initial driver framework
Date: Tue, 18 Feb 2025 14:19:03 -0800 [thread overview]
Message-ID: <39ec35d0-56a2-4473-a67d-9a6727c61693@amd.com> (raw)
In-Reply-To: <20250218195132.GB53094@unreal>
On 2/18/2025 11:51 AM, Leon Romanovsky wrote:
>
> On Tue, Feb 11, 2025 at 03:48:52PM -0800, Shannon Nelson wrote:
>> Initial files for adding a new fwctl driver for the AMD/Pensando PDS
>> devices. This sets up a simple auxiliary_bus driver that registers
>> with fwctl subsystem. It expects that a pds_core device has set up
>> the auxiliary_device pds_core.fwctl
>>
>> Signed-off-by: Shannon Nelson <shannon.nelson@amd.com>
>> ---
>> MAINTAINERS | 7 ++
>> drivers/fwctl/Kconfig | 10 ++
>> drivers/fwctl/Makefile | 1 +
>> drivers/fwctl/pds/Makefile | 4 +
>> drivers/fwctl/pds/main.c | 195 +++++++++++++++++++++++++++++++++
>> include/linux/pds/pds_adminq.h | 77 +++++++++++++
>> include/uapi/fwctl/fwctl.h | 1 +
>> include/uapi/fwctl/pds.h | 27 +++++
>> 8 files changed, 322 insertions(+)
>> create mode 100644 drivers/fwctl/pds/Makefile
>> create mode 100644 drivers/fwctl/pds/main.c
>> create mode 100644 include/uapi/fwctl/pds.h
>
> <...>
>
>> +static int pdsfc_open_uctx(struct fwctl_uctx *uctx)
>> +{
>> + struct pdsfc_dev *pdsfc = container_of(uctx->fwctl, struct pdsfc_dev, fwctl);
>> + struct pdsfc_uctx *pdsfc_uctx = container_of(uctx, struct pdsfc_uctx, uctx);
>> + struct device *dev = &uctx->fwctl->dev;
>> +
>> + dev_dbg(dev, "%s: caps = 0x%04x\n", __func__, pdsfc->caps);
>
> This driver is too noisy and has too many debug/err prints.
Yes, still being worked on, but also we used dbp prints to keep the
noise to a minimum. Most of these will disappear as we move out of RFC
mode.
>
>> + pdsfc_uctx->uctx_caps = pdsfc->caps;
>> +
>> + return 0;
>> +}
>> +
>> +static void pdsfc_close_uctx(struct fwctl_uctx *uctx)
>> +{
>> +}
>> +
>> +static void *pdsfc_info(struct fwctl_uctx *uctx, size_t *length)
>> +{
>> + struct pdsfc_uctx *pdsfc_uctx = container_of(uctx, struct pdsfc_uctx, uctx);
>> + struct fwctl_info_pds *info;
>> +
>> + info = kzalloc(sizeof(*info), GFP_KERNEL);
>> + if (!info)
>> + return ERR_PTR(-ENOMEM);
>> +
>> + info->uctx_caps = pdsfc_uctx->uctx_caps;
>> +
>> + return info;
>> +}
>> +
>> +static void pdsfc_free_ident(struct pdsfc_dev *pdsfc)
>> +{
>> + struct device *dev = &pdsfc->fwctl.dev;
>> +
>> + if (pdsfc->ident) {
>
> It is not kernel style, which is success oriented.
> If (!pdsfc->ident)
> return;
>
> However I don't know how can this happen. You shouldn't call to pdsfc_free_ident
> if ident wasn't set.
This will change as we rework the ident handling to simply cache it and
immediately drop the DMA linkage as suggested by an earlier review.
>
>> + dma_free_coherent(dev, sizeof(*pdsfc->ident),
>> + pdsfc->ident, pdsfc->ident_pa);
>> + pdsfc->ident = NULL;
>
> Please don't assign NULL to pointers if they are not reused.
>
>> + pdsfc->ident_pa = DMA_MAPPING_ERROR;
>
> Same.
>
>> + }
>> +}
>> +
>> +static int pdsfc_identify(struct pdsfc_dev *pdsfc)
>> +{
>> + struct device *dev = &pdsfc->fwctl.dev;
>> + union pds_core_adminq_comp comp = {0};
>> + union pds_core_adminq_cmd cmd = {0};
>> + struct pds_fwctl_ident *ident;
>> + dma_addr_t ident_pa;
>> + int err = 0;
>
> There is no need to assign 0 to err.
>
>> +
>> + ident = dma_alloc_coherent(dev->parent, sizeof(*ident), &ident_pa, GFP_KERNEL);
>> + err = dma_mapping_error(dev->parent, ident_pa);
>> + if (err) {
>> + dev_err(dev, "Failed to map ident\n");
>
> This is one of the examples of such extra prints.
>
>> + return err;
>> + }
>> +
>> + cmd.fwctl_ident.opcode = PDS_FWCTL_CMD_IDENT;
>> + cmd.fwctl_ident.version = 0;
>
> How will you manage this version field?
Since there is only version 0 at this point, there is not much to
manage. I wanted to explicitly show the setting to version 0, but maybe
that can be assumed by the basic struct init.
>
>> + cmd.fwctl_ident.len = cpu_to_le32(sizeof(*ident));
>> + cmd.fwctl_ident.ident_pa = cpu_to_le64(ident_pa);
>> +
>> + err = pds_client_adminq_cmd(pdsfc->padev, &cmd, sizeof(cmd), &comp, 0);
>> + if (err) {
>> + dma_free_coherent(dev->parent, PAGE_SIZE, ident, ident_pa);
>> + dev_err(dev, "Failed to send adminq cmd opcode: %u entity: %u err: %d\n",
>> + cmd.fwctl_query.opcode, cmd.fwctl_query.entity, err);
>> + return err;
>> + }
>> +
>> + pdsfc->ident = ident;
>> + pdsfc->ident_pa = ident_pa;
>> +
>> + dev_dbg(dev, "ident: version %u max_req_sz %u max_resp_sz %u max_req_sg_elems %u max_resp_sg_elems %u\n",
>> + ident->version, ident->max_req_sz, ident->max_resp_sz,
>> + ident->max_req_sg_elems, ident->max_resp_sg_elems);
>> +
>> + return 0;
>> +}
>> +
>> +static void *pdsfc_fw_rpc(struct fwctl_uctx *uctx, enum fwctl_rpc_scope scope,
>> + void *in, size_t in_len, size_t *out_len)
>> +{
>> + return NULL;
>> +}
>> +
>> +static const struct fwctl_ops pdsfc_ops = {
>> + .device_type = FWCTL_DEVICE_TYPE_PDS,
>> + .uctx_size = sizeof(struct pdsfc_uctx),
>> + .open_uctx = pdsfc_open_uctx,
>> + .close_uctx = pdsfc_close_uctx,
>> + .info = pdsfc_info,
>> + .fw_rpc = pdsfc_fw_rpc,
>> +};
>> +
>> +static int pdsfc_probe(struct auxiliary_device *adev,
>> + const struct auxiliary_device_id *id)
>> +{
>> + struct pdsfc_dev *pdsfc __free(pdsfc_dev);
>> + struct pds_auxiliary_dev *padev;
>> + struct device *dev = &adev->dev;
>> + int err = 0;
>> +
>> + padev = container_of(adev, struct pds_auxiliary_dev, aux_dev);
>> + pdsfc = fwctl_alloc_device(&padev->vf_pdev->dev, &pdsfc_ops,
>> + struct pdsfc_dev, fwctl);
>> + if (!pdsfc) {
>> + dev_err(dev, "Failed to allocate fwctl device struct\n");
>> + return -ENOMEM;
>> + }
>> + pdsfc->padev = padev;
>> +
>> + err = pdsfc_identify(pdsfc);
>> + if (err) {
>> + dev_err(dev, "Failed to identify device, err %d\n", err);
>> + return err;
>> + }
>> +
>> + err = fwctl_register(&pdsfc->fwctl);
>> + if (err) {
>> + dev_err(dev, "Failed to register device, err %d\n", err);
>> + return err;
>> + }
>> +
>> + auxiliary_set_drvdata(adev, no_free_ptr(pdsfc));
>> +
>> + return 0;
>> +
>> +free_ident:
>> + pdsfc_free_ident(pdsfc);
>> + return err;
>> +}
>> +
>> +static void pdsfc_remove(struct auxiliary_device *adev)
>> +{
>> + struct pdsfc_dev *pdsfc __free(pdsfc_dev) = auxiliary_get_drvdata(adev);
>> +
>> + fwctl_unregister(&pdsfc->fwctl);
>> + pdsfc_free_ident(pdsfc);
>> +}
>> +
>> +static const struct auxiliary_device_id pdsfc_id_table[] = {
>> + {.name = PDS_CORE_DRV_NAME "." PDS_DEV_TYPE_FWCTL_STR },
>> + {}
>> +};
>> +MODULE_DEVICE_TABLE(auxiliary, pdsfc_id_table);
>> +
>> +static struct auxiliary_driver pdsfc_driver = {
>> + .name = "pds_fwctl",
>> + .probe = pdsfc_probe,
>> + .remove = pdsfc_remove,
>> + .id_table = pdsfc_id_table,
>> +};
>> +
>> +module_auxiliary_driver(pdsfc_driver);
>> +
>> +MODULE_IMPORT_NS(FWCTL);
>> +MODULE_DESCRIPTION("pds fwctl driver");
>> +MODULE_AUTHOR("Shannon Nelson <shannon.nelson@amd.com>");
>> +MODULE_AUTHOR("Brett Creeley <brett.creeley@amd.com>");
>> +MODULE_LICENSE("Dual BSD/GPL");
>> diff --git a/include/linux/pds/pds_adminq.h b/include/linux/pds/pds_adminq.h
>> index 4b4e9a98b37b..7fc353b63353 100644
>> --- a/include/linux/pds/pds_adminq.h
>> +++ b/include/linux/pds/pds_adminq.h
>> @@ -1179,6 +1179,78 @@ struct pds_lm_host_vf_status_cmd {
>> u8 status;
>> };
>>
>> +enum pds_fwctl_cmd_opcode {
>> + PDS_FWCTL_CMD_IDENT = 70,
>
> Please try to avoid from vertical space alignment. It doesn't survive
> time and at some point you will need to reformat it, which will cause
> to churn and harm backporting/stable without any reason.
Yeah, that was inherited from earlier work not necessary here.
>
> Thanks
Thanks for your time amd comments,
sln
next prev parent reply other threads:[~2025-02-18 22:19 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 [this message]
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 ` [RFC PATCH fwctl 0/5] pds_fwctl: fwctl for AMD/Pensando core devices Andrew Lunn
2025-02-12 14:43 ` 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=39ec35d0-56a2-4473-a67d-9a6727c61693@amd.com \
--to=shannon.nelson@amd.com \
--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 \
/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).