From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <dan.j.williams@intel.com>,
<ira.weiny@intel.com>, <vishal.l.verma@intel.com>,
<alison.schofield@intel.com>, <dave@stgolabs.net>,
<jgg@nvidia.com>, <shiju.jose@huawei.com>
Subject: Re: [PATCH v5 07/15] cxl: Add FWCTL support to CXL
Date: Wed, 12 Feb 2025 17:47:09 +0000 [thread overview]
Message-ID: <20250212174709.000013d1@huawei.com> (raw)
In-Reply-To: <20250212174440.0000701c@huawei.com>
On Wed, 12 Feb 2025 17:44:40 +0000
Jonathan Cameron <Jonathan.Cameron@huawei.com> wrote:
> On Tue, 11 Feb 2025 11:28:01 -0700
> Dave Jiang <dave.jiang@intel.com> wrote:
>
> > Add fwctl support code to allow sending of CXL feature commands from
> > userspace through as ioctls via FWCTL. Provide initial setup bits. The
> > CXL PCI probe function will call cxl_setup_fwctl() after the cxl_memdev
> > has been enumerated in order to setup FWCTL char device under the
> > cxl_memdev like the existing memdev char device for issuing CXL raw
> > mailbox commands from userspace via ioctls.
> >
> > Signed-off-by: Dave Jiang <dave.jiang@intel.com>
>
> A comment inline, but not a request to change anything for this
> series. More a suspicion that the simplification Dan suggested
> will bite later :)
>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> > diff --git a/drivers/cxl/core/features.c b/drivers/cxl/core/features.c
> > index 02558f46883d..db48a8fbde81 100644
> > --- a/drivers/cxl/core/features.c
> > +++ b/drivers/cxl/core/features.c
> > @@ -1,5 +1,6 @@
>
> > +
> > +int devm_cxl_setup_fwctl(struct cxl_memdev *cxlmd)
>
> I slightly wonder if we would be better passing
> struct device *parent, struct cxl_dev_state *cxlds.
>
> However, that can happen if this gets reuse I guess
> rather than now. We might have to put back a specific
> fwctl structure to enable that given we could know
> where to find cxlds in the structure containing the parent
> device though.
>
> Meh, might be my problem if I try to reuse this for
> switch-cci which is my plan if I get time to do an RFC / PoC.
Actually no, that's garbage. I'll need to do a custom
fwctl device anyway even if it shares userspace interface with
this because it makes no real sense to have a cxlds either.
Definitely keep it as is!
Jonathan
>
>
>
> > +{
> > + struct cxl_dev_state *cxlds = cxlmd->cxlds;
> > + struct cxl_features_state *cxlfs;
> > + int rc;
> > +
> > + cxlfs = to_cxlfs(cxlds);
> > + if (!cxlfs)
> > + return -ENODEV;
> > +
> > + /* No need to setup FWCTL if there are no user allowed features found */
> > + if (!cxlfs->entries->num_user_features)
> > + return -ENODEV;
> > +
> > + struct fwctl_device *fwctl_dev __free(free_fwctl_dev) =
> > + _fwctl_alloc_device(&cxlmd->dev, &cxlctl_ops, sizeof(*fwctl_dev));
> > + if (!fwctl_dev)
> > + return -ENOMEM;
> > +
> > + rc = fwctl_register(fwctl_dev);
> > + if (rc)
> > + return rc;
> > +
> > + cxlfs->fwctl_dev = fwctl_dev;
> > +
> > + return devm_add_action_or_reset(&cxlmd->dev, free_memdev_fwctl,
> > + no_free_ptr(fwctl_dev));
> > +}
> > +EXPORT_SYMBOL_NS_GPL(devm_cxl_setup_fwctl, "CXL");
> > +
> > +MODULE_IMPORT_NS("FWCTL");
>
next prev parent reply other threads:[~2025-02-12 17:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 18:27 [PATCH v5 00/15] cxl: Add CXL feature commands support via fwctl Dave Jiang
2025-02-11 18:27 ` [PATCH v5 01/15] cxl: Enumerate feature commands Dave Jiang
2025-02-11 18:27 ` [PATCH v5 02/15] cxl: Add Get Supported Features command for kernel usage Dave Jiang
2025-02-11 18:27 ` [PATCH v5 03/15] cxl/test: Add Get Supported Features mailbox command support Dave Jiang
2025-02-11 18:27 ` [PATCH v5 04/15] cxl/mbox: Add GET_FEATURE mailbox command Dave Jiang
2025-02-11 18:27 ` [PATCH v5 05/15] cxl/mbox: Add SET_FEATURE " Dave Jiang
2025-02-12 17:35 ` Jonathan Cameron
2025-02-11 18:28 ` [PATCH v5 06/15] cxl: Setup exclusive CXL features that are reserved for the kernel Dave Jiang
2025-02-11 18:28 ` [PATCH v5 07/15] cxl: Add FWCTL support to CXL Dave Jiang
2025-02-12 17:44 ` Jonathan Cameron
2025-02-12 17:47 ` Jonathan Cameron [this message]
2025-02-11 18:28 ` [PATCH v5 08/15] cxl: Add support for FWCTL get driver information callback Dave Jiang
2025-02-12 21:18 ` Saeed Mahameed
2025-02-13 15:32 ` Jason Gunthorpe
2025-02-13 17:29 ` Dave Jiang
2025-02-13 18:33 ` Dan Williams
2025-02-13 18:43 ` Jason Gunthorpe
2025-02-13 17:27 ` Dave Jiang
2025-02-13 18:12 ` Dan Williams
2025-02-13 22:11 ` Dave Jiang
2025-02-13 19:36 ` Jason Gunthorpe
2025-02-13 22:11 ` Dave Jiang
2025-02-11 18:28 ` [PATCH v5 09/15] cxl: Move cxl feature command structs to user header Dave Jiang
2025-02-11 18:28 ` [PATCH v5 10/15] cxl: Add support for fwctl RPC command to enable CXL feature commands Dave Jiang
2025-02-12 17:55 ` Jonathan Cameron
2025-02-12 23:37 ` Jason Gunthorpe
2025-02-13 2:49 ` Saeed Mahameed
2025-02-13 18:05 ` Jason Gunthorpe
2025-02-13 18:22 ` Dan Williams
2025-02-13 22:16 ` Dave Jiang
2025-02-11 18:28 ` [PATCH v5 11/15] cxl: Add support to handle user feature commands for get feature Dave Jiang
2025-02-11 18:28 ` [PATCH v5 12/15] cxl: Add support to handle user feature commands for set feature Dave Jiang
2025-02-11 18:28 ` [PATCH v5 13/15] cxl/test: Add Get Feature support to cxl_test Dave Jiang
2025-02-11 18:28 ` [PATCH v5 14/15] cxl/test: Add Set " Dave Jiang
2025-02-11 18:28 ` [PATCH v5 15/15] fwctl/cxl: Add documentation to FWCTL CXL Dave Jiang
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=20250212174709.000013d1@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jgg@nvidia.com \
--cc=linux-cxl@vger.kernel.org \
--cc=shiju.jose@huawei.com \
--cc=vishal.l.verma@intel.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