From: Dave Jiang <dave.jiang@intel.com>
To: Dan Williams <dan.j.williams@intel.com>, linux-cxl@vger.kernel.org
Cc: ira.weiny@intel.com, vishal.l.verma@intel.com,
alison.schofield@intel.com, Jonathan.Cameron@huawei.com,
dave@stgolabs.net, jgg@nvidia.com, shiju.jose@huawei.com
Subject: Re: [PATCH v4 02/15] cxl: Add Get Supported Features command for kernel usage
Date: Mon, 10 Feb 2025 10:03:58 -0700 [thread overview]
Message-ID: <8b271a9e-2576-42d5-af84-b7ddac01f67b@intel.com> (raw)
In-Reply-To: <67a69dc5c3cd5_2d1e294fc@dwillia2-xfh.jf.intel.com.notmuch>
On 2/7/25 4:56 PM, Dan Williams wrote:
> Dave Jiang wrote:
>> CXL spec r3.2 8.2.9.6.1 Get Supported Features (Opcode 0500h)
>> The command retrieve the list of supported device-specific features
>> (identified by UUID) and general information about each Feature.
>>
>> The driver will retrieve the Feature entries in order to make checks and
>> provide information for the Get Feature and Set Feature command. One of
>> the main piece of information retrieved are the effects a Set Feature
>> command would have for a particular feature. The retrieved Feature
>> entries are stored in the cxl_mailbox context.
>>
>> The setup of Features is initiated via devm_cxl_setup_features() during the
>> pci probe function before the cxl_memdev is enumerated.
>>
>> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> [..]
>> +/**
>> + * devm_cxl_setup_features() - Allocate and initialize features context
>> + * @cxlds: CXL device context
>> + *
>> + * Return 0 on success or -errno on failure.
>> + */
>> +int devm_cxl_setup_features(struct cxl_dev_state *cxlds)
>> +{
>> + struct cxl_mailbox *cxl_mbox = &cxlds->cxl_mbox;
>> + int rc;
>> +
>> + if (cxl_mbox->feat_cap < CXL_FEATURES_RO)
>> + return -ENODEV;
>> +
>> + struct cxl_features_state *cxlfs __free(kfree) =
>> + kzalloc(sizeof(*cxlfs), GFP_KERNEL);
>> + if (!cxlfs)
>> + return -ENOMEM;
>> +
>> + cxlfs->cxlds = cxlds;
>> +
>> + cxlfs->entries = get_supported_features(cxlfs);
>> + if (!cxlfs->entries)
>> + return -ENOMEM;
>> +
>> + cxlds->cxlfs = cxlfs;
>> + rc = devm_add_action_or_reset(cxlds->dev, free_cxlfs, no_free_ptr(cxlfs));
>> + if (rc)
>> + return rc;
>> +
>> + return 0;
>
> One small cleanup you can do here when applying is reduce these last 5
> lines to:
>
> return devm_add_action_or_reset(cxlds->dev, free_cxlfs,
> no_free_ptr(cxlfs));
>
> [..]
>> +/**
>> + * struct cxl_features_state - The Features state for the device
>> + * @cxlds: Pointer to CXL device state
>> + * @cap: Feature commands capability
>> + * @entries: CXl feature entry context
>> + * @num_features: total Features supported by the device
>> + * @ent: Flex array of Feature detail entries from the device
>> + */
>> +struct cxl_features_state {
>> + struct cxl_dev_state *cxlds;
>> + struct cxl_feat_entries {
>> + int num_features;
>> + struct cxl_feat_entry ent[] __counted_by(num_features);
>> + } *entries;
>> +};
>> +
>> +#ifdef CONFIG_CXL_FEATURES
>> +inline struct cxl_features_state *to_cxlfs(struct cxl_dev_state *cxlds);
>
> Shouldn't this be:
>
> static inline struct cxl_features_state *to_cxlfs(struct cxl_dev_state *cxlds)
> {
> return cxlds->cxlfs;
> }
>
> ...no need to do an out of line function for this.
So the reason it is an out of line function is to not expose 'struct cxl_dev_state' globally. Otherwise it needs to be in a public header in include/cxl/ to work.
DJ
>
> Another small fixup you can do when applying.
>
> Otherwise, this now all looks good to me:
>
> Reviewed-by: Dan Williams <dan.j.williams@intel.com>
next prev parent reply other threads:[~2025-02-10 17:04 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 23:37 [PATCH v4 00/15] cxl: Add CXL feature commands support via fwctl Dave Jiang
2025-02-07 23:37 ` [PATCH v4 01/15] cxl: Enumerate feature commands Dave Jiang
2025-02-07 23:47 ` Dan Williams
2025-02-08 6:00 ` Li Ming
2025-02-11 17:05 ` Jonathan Cameron
2025-02-07 23:37 ` [PATCH v4 02/15] cxl: Add Get Supported Features command for kernel usage Dave Jiang
2025-02-07 23:56 ` Dan Williams
2025-02-10 17:03 ` Dave Jiang [this message]
2025-02-08 6:13 ` Li Ming
2025-02-10 17:06 ` Dave Jiang
2025-02-07 23:37 ` [PATCH v4 03/15] cxl/test: Add Get Supported Features mailbox command support Dave Jiang
2025-02-07 23:37 ` [PATCH v4 04/15] cxl/mbox: Add GET_FEATURE mailbox command Dave Jiang
2025-02-08 0:12 ` Dan Williams
2025-02-07 23:37 ` [PATCH v4 05/15] cxl/mbox: Add SET_FEATURE " Dave Jiang
2025-02-08 0:21 ` Dan Williams
2025-02-08 6:17 ` Li Ming
2025-02-07 23:37 ` [PATCH v4 06/15] cxl: Setup exclusive CXL features that are reserved for the kernel Dave Jiang
2025-02-08 1:10 ` Dan Williams
2025-02-08 1:16 ` Dave Jiang
2025-02-08 6:22 ` Li Ming
2025-02-10 17:40 ` Dave Jiang
2025-02-10 17:50 ` Dave Jiang
2025-02-11 5:46 ` Li Ming
2025-02-11 16:13 ` Dave Jiang
2025-02-07 23:37 ` [PATCH v4 07/15] cxl: Add FWCTL support to CXL Dave Jiang
2025-02-08 1:24 ` Dan Williams
2025-02-07 23:37 ` [PATCH v4 08/15] cxl: Add support for FWCTL get driver information callback Dave Jiang
2025-02-08 1:25 ` Dan Williams
2025-02-10 6:21 ` Li Ming
2025-02-07 23:37 ` [PATCH v4 09/15] cxl: Move cxl feature command structs to user header Dave Jiang
2025-02-07 23:37 ` [PATCH v4 10/15] cxl: Add support for fwctl RPC command to enable CXL feature commands Dave Jiang
2025-02-08 1:29 ` Dan Williams
2025-02-08 1:34 ` Dan Williams
2025-02-08 7:09 ` Li Ming
2025-02-10 22:31 ` Dave Jiang
2025-02-07 23:37 ` [PATCH v4 11/15] cxl: Add support to handle user feature commands for get feature Dave Jiang
2025-02-10 6:41 ` Li Ming
2025-02-07 23:37 ` [PATCH v4 12/15] cxl: Add support to handle user feature commands for set feature Dave Jiang
2025-02-10 6:43 ` Li Ming
2025-02-07 23:37 ` [PATCH v4 13/15] cxl/test: Add Get Feature support to cxl_test Dave Jiang
2025-02-10 6:44 ` Li Ming
2025-02-07 23:37 ` [PATCH v4 14/15] cxl/test: Add Set " Dave Jiang
2025-02-10 6:44 ` Li Ming
2025-02-07 23:37 ` [PATCH v4 15/15] fwctl/cxl: Add documentation to FWCTL CXL Dave Jiang
2025-02-08 1:38 ` Dan Williams
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=8b271a9e-2576-42d5-af84-b7ddac01f67b@intel.com \
--to=dave.jiang@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@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