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 v2 03/16] cxl: Add Get Supported Features command for kernel usage
Date: Mon, 3 Feb 2025 12:19:14 +0000 [thread overview]
Message-ID: <20250203121914.00002b30@huawei.com> (raw)
In-Reply-To: <20250201004459.466499-4-dave.jiang@intel.com>
On Fri, 31 Jan 2025 17:41:56 -0700
Dave Jiang <dave.jiang@intel.com> 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.
>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> v2:
> - Move to memdev driver and drop features driver support. (Dan)
> - Use features_capability to check what's supported. (Dan)
> - Drop cxl_get_supported_feature_entry() as no usage (Dan, Jonathan)
> - Drop Shiju sign off tags per requested. (Shiju)
> - Rename EXTEND bit(9) to VALID. (Jonathan)
I've read this code too many times :(
Anyhow some feedback on stuff I think belongs in patch 2 and
use of struct_size() to make the sizing calcs more obvious that
I'd missed until now.
> +static int get_supported_features(struct cxl_memdev *cxlmd,
> + struct cxl_features_state *cxlfs)
> +{
> + int remain_feats, max_size, max_feats, start, rc, hdr_size;
> + struct cxl_mailbox *cxl_mbox = &cxlmd->cxlds->cxl_mbox;
> + int feat_size = sizeof(struct cxl_feat_entry);
> + struct cxl_mbox_get_sup_feats_in mbox_in;
> + struct cxl_feat_entry *entry;
> + struct cxl_mbox_cmd mbox_cmd;
> + int count;
> +
> + if (cxlfs->cap < CXL_FEATURES_RO)
> + return -EOPNOTSUPP;
> +
> + count = cxl_get_supported_features_count(cxl_mbox);
> + if (count == 0)
> + return 0;
Not sure this should return 0. That will leave the cxlfs
in place. + your outermost call in the mem driver prints
a message saying nothing found only if an error is returned.
> + if (count < 0)
> + return -ENXIO;
> +
> + struct cxl_feat_entry *entries __free(kvfree) =
> + kvmalloc(count * sizeof(*entries), GFP_KERNEL);
> + if (!entries)
> + return -ENOMEM;
> +
> + struct cxl_mbox_get_sup_feats_out *mbox_out __free(kvfree) =
> + kvmalloc(cxl_mbox->payload_size, GFP_KERNEL);
> + if (!mbox_out)
> + return -ENOMEM;
> +
> + hdr_size = sizeof(*mbox_out);
May seem an odd request but can we make this
struct_size(mbox_out, ents, 0)
as it seems odd to say how big is this thing we just allocated
and get a smaller size (though correct given the trailing [] array)
> + max_size = cxl_mbox->payload_size - hdr_size;
> + /* max feat entries that can fit in mailbox max payload size */
> + max_feats = max_size / feat_size;
> + entry = entries;
> +
> + start = 0;
> + remain_feats = count;
> + do {
> + int retrieved, alloc_size, copy_feats;
> + int num_entries;
> +
> + if (remain_feats > max_feats) {
> + alloc_size = sizeof(*mbox_out) + max_feats * feat_size;
alloc_size = struct_size(mbox_out, ents, max_feats);
> + remain_feats = remain_feats - max_feats;
> + copy_feats = max_feats;
> + } else {
> + alloc_size = sizeof(*mbox_out) + remain_feats * feat_size;
alloc_size = struct_size(mbox_out, ents, remain_feats);
> + copy_feats = remain_feats;
> + remain_feats = 0;
> + }
> +
> + memset(&mbox_in, 0, sizeof(mbox_in));
> + mbox_in.count = cpu_to_le32(alloc_size);
> + mbox_in.start_idx = cpu_to_le16(start);
> + memset(mbox_out, 0, alloc_size);
> + mbox_cmd = (struct cxl_mbox_cmd) {
> + .opcode = CXL_MBOX_OP_GET_SUPPORTED_FEATURES,
> + .size_in = sizeof(mbox_in),
> + .payload_in = &mbox_in,
> + .size_out = alloc_size,
> + .payload_out = mbox_out,
> + .min_out = hdr_size,
> + };
> + rc = cxl_internal_send_cmd(cxl_mbox, &mbox_cmd);
> + if (rc < 0)
> + return rc;
> +
> + if (mbox_cmd.size_out <= hdr_size)
> + return -ENXIO;
> +
> + /*
> + * Make sure retrieved out buffer is multiple of feature
> + * entries.
> + */
> + retrieved = mbox_cmd.size_out - hdr_size;
> + if (retrieved % feat_size)
> + return -ENXIO;
> +
> + num_entries = le16_to_cpu(mbox_out->num_entries);
> + /*
> + * If the reported output entries * defined entry size !=
> + * retrieved output bytes, then the output package is incorrect.
> + */
> + if (num_entries * feat_size != retrieved)
> + return -ENXIO;
> +
> + memcpy(entry, mbox_out->ents, retrieved);
> + entry++;
> + /*
> + * If the number of output entries is less than expected, add the
> + * remaining entries to the next batch.
> + */
> + remain_feats += copy_feats - num_entries;
> + start += num_entries;
> + } while (remain_feats);
> +
> + cxlfs->num_features = count;
> + cxlfs->entries = no_free_ptr(entries);
> + return devm_add_action_or_reset(&cxlmd->dev, cxl_free_feature_entries,
> + cxlfs->entries);
> +}
> +
> +static void enumerate_feature_cmds(struct cxl_memdev *cxlmd,
> + struct cxl_features_state *cxlfs)
Good. Suggested this in previous.
> {
> struct cxl_dev_state *cxlds = cxlmd->cxlds;
> struct cxl_mailbox *cxl_mbox = &cxlds->cxl_mbox;
> - struct cxl_features_state *cxlfs = cxlds->cxlmd->cxlfs;
And you drop the circular line. Push this into patch 2.
> int fid;
>
> fid = cxl_get_feature_command_id(CXL_MBOX_OP_GET_SUPPORTED_FEATURES);
> @@ -31,6 +164,15 @@ static void enumerate_feature_cmds(struct cxl_memdev *cxlmd)
> cxlfs->cap = CXL_FEATURES_RW;
> }
>
> +static void cxl_cxlfs_free(struct cxl_features_state *cxlfs)
> +{
> + struct device *dev = &cxlfs->cxlmd->dev;
> +
> + devm_kfree(dev, cxlfs);
As below. Let's bring cleanup here if we have to unset cxlmd->cxlfs
later.
> +}
> +
> +DEFINE_FREE(free_cxlfs, struct cxl_features_state *, if (_T) cxl_cxlfs_free(_T))
> +
> /**
> * devm_cxl_add_features() - Allocate and initialize features context
> * @cxlmd: CXL memory device
> @@ -39,16 +181,21 @@ static void enumerate_feature_cmds(struct cxl_memdev *cxlmd)
> */
> int devm_cxl_add_features(struct cxl_memdev *cxlmd)
> {
> - struct cxl_features_state *cxlfs;
> struct device *dev = &cxlmd->dev;
> + int rc;
>
> - cxlfs = devm_kzalloc(dev, sizeof(*cxlfs), GFP_KERNEL);
> + struct cxl_features_state *cxlfs __free(free_cxlfs) =
> + devm_kzalloc(dev, sizeof(*cxlfs), GFP_KERNEL);
This line changes 3 times in the series. Can we drag the
last one here (as per comment on patch 2) by introducing
the new allocate function at this point.
> if (!cxlfs)
> return -ENOMEM;
>
> - cxlmd->cxlfs = cxlfs;
> cxlfs->cxlmd = cxlmd;
> - enumerate_feature_cmds(cxlmd);
> + enumerate_feature_cmds(cxlmd, cxlfs);
> + rc = get_supported_features(cxlmd, cxlfs);
> + if (rc)
> + return rc;
> +
> + cxlmd->cxlfs = no_free_ptr(cxlfs);
>
> return 0;
> }
next prev parent reply other threads:[~2025-02-03 12:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-01 0:41 [PATCH v2 0/16] cxl: Add CXL feature commands support via fwctl Dave Jiang
2025-02-01 0:41 ` [PATCH v2 01/16] cxl: Refactor user ioctl command path from mds to mailbox Dave Jiang
2025-02-01 0:41 ` [PATCH v2 02/16] cxl: Enumerate feature commands Dave Jiang
2025-02-03 12:06 ` Jonathan Cameron
2025-02-03 23:23 ` Dave Jiang
2025-02-01 0:41 ` [PATCH v2 03/16] cxl: Add Get Supported Features command for kernel usage Dave Jiang
2025-02-03 12:19 ` Jonathan Cameron [this message]
2025-02-01 0:41 ` [PATCH v2 04/16] cxl/test: Add Get Supported Features mailbox command support Dave Jiang
2025-02-03 12:22 ` Jonathan Cameron
2025-02-01 0:41 ` [PATCH v2 05/16] cxl/mbox: Add GET_FEATURE mailbox command Dave Jiang
2025-02-01 0:41 ` [PATCH v2 06/16] cxl/mbox: Add SET_FEATURE " Dave Jiang
2025-02-03 12:27 ` Jonathan Cameron
2025-02-01 0:42 ` [PATCH v2 07/16] cxl: Setup exclusive CXL features that are reserved for the kernel Dave Jiang
2025-02-01 0:42 ` [PATCH v2 08/16] cxl: Add FWCTL support to the CXL memdev driver Dave Jiang
2025-02-01 1:04 ` Dave Jiang
2025-02-03 12:42 ` Jonathan Cameron
2025-02-03 14:25 ` Jason Gunthorpe
2025-02-03 16:22 ` Dave Jiang
2025-02-03 16:30 ` Jason Gunthorpe
2025-02-01 0:42 ` [PATCH v2 09/16] cxl: Add support for FWCTL get driver information callback Dave Jiang
2025-02-03 12:43 ` Jonathan Cameron
2025-02-01 0:42 ` [PATCH v2 10/16] cxl: Move cxl feature command structs to user header Dave Jiang
2025-02-01 0:42 ` [PATCH v2 11/16] cxl: Add support for fwctl RPC command to enable CXL feature commands Dave Jiang
2025-02-03 13:03 ` Jonathan Cameron
2025-02-01 0:42 ` [PATCH v2 12/16] cxl: Add support to handle user feature commands for get feature Dave Jiang
2025-02-01 0:42 ` [PATCH v2 13/16] cxl: Add support to handle user feature commands for set feature Dave Jiang
2025-02-01 0:42 ` [PATCH v2 14/16] cxl/test: Add Get Feature support to cxl_test Dave Jiang
2025-02-01 0:42 ` [PATCH v2 15/16] cxl/test: Add Set " Dave Jiang
2025-02-01 0:42 ` [PATCH v2 16/16] fwctl/cxl: Add documentation to FWCTL CXL Dave Jiang
2025-02-03 13:08 ` Jonathan Cameron
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=20250203121914.00002b30@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