From: Dan Williams <dan.j.williams@intel.com>
To: Dave Jiang <dave.jiang@intel.com>, <linux-cxl@vger.kernel.org>
Cc: <dan.j.williams@intel.com>, <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 v3 11/16] cxl: Add support for fwctl RPC command to enable CXL feature commands
Date: Tue, 4 Feb 2025 17:41:06 -0800 [thread overview]
Message-ID: <67a2c1b1ee289_2d2c2941e@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20250204220430.4146187-12-dave.jiang@intel.com>
Dave Jiang wrote:
> fwctl provides a fwctl_ops->fw_rpc() callback in order to issue ioctls
> to a device. The cxl fwctl driver will start by supporting the CXL
> feature commands: Get Supported Features, Get Feature, and Set Feature.
>
> The fw_rpc() callback provides 'enum fwctl_rpc_scope' parameter where
> it indicates the security scope of the call. The Get Supported Features
> and Get Feature calls can be executed with the scope of
> FWCTL_RPC_CONFIGRATION. The Set Feature call is gated by the effects
> of the feature reported by Get Supported Features call for the specific
> feature.
>
> Only "get supported features" is supported in this patch. Additional
> commands will be added in follow on patches. "Get supported features"
> will filter the features that are exclusive to the kernel and only
> report out features that are not kernel only.
>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> v3:
> - Cleanup for loop initializers. (Jonathan)
> - Move is_cxl_feature_exclusive() prototype. (Jonathan)
> - Move cxlctl_fwc_rpc() input param name change. (Jonathan)
> - Use struct_size() for calculation. (Jonathan)
> ---
> drivers/cxl/core/mbox.c | 9 ++
> drivers/cxl/cxl.h | 1 +
> drivers/cxl/fwctl.c | 200 +++++++++++++++++++++++++++++++++++-
> include/cxl/features.h | 8 --
> include/uapi/cxl/features.h | 1 +
> include/uapi/fwctl/cxl.h | 37 +++++++
> 6 files changed, 246 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/cxl/core/mbox.c b/drivers/cxl/core/mbox.c
> index 9fe552e3d465..d38a5fc1384f 100644
> --- a/drivers/cxl/core/mbox.c
> +++ b/drivers/cxl/core/mbox.c
> @@ -92,6 +92,15 @@ int cxl_get_feature_command_id(u16 opcode)
> }
> EXPORT_SYMBOL_NS_GPL(cxl_get_feature_command_id, "CXL");
>
> +u16 cxl_get_feature_command_opcode(int feature_id)
> +{
> + if (feature_id >= ARRAY_SIZE(cxl_feature_commands))
> + return 0xffff;
> +
> + return cxl_feature_commands[feature_id];
> +}
> +EXPORT_SYMBOL_NS_GPL(cxl_get_feature_command_opcode, "CXL");
This can move to drivers/cxl/core/features.c, and it looks like
@feature_id and @cxl_feature_commands are misnamed.
This should be named in terms of fwctl command id to CXL opcode, right?
> +
> /*
> * Commands that RAW doesn't permit. The rationale for each:
> *
> diff --git a/drivers/cxl/cxl.h b/drivers/cxl/cxl.h
> index 2d6f7c87e5e8..451b2c7e995b 100644
> --- a/drivers/cxl/cxl.h
> +++ b/drivers/cxl/cxl.h
> @@ -912,6 +912,7 @@ void cxl_coordinates_combine(struct access_coordinate *out,
> bool cxl_endpoint_decoder_reset_detected(struct cxl_port *port);
>
> int cxl_get_feature_command_id(u16 opcode);
> +u16 cxl_get_feature_command_opcode(int feature_id);
>
> /*
> * Unit test builds overrides this to __weak, find the 'strong' version
> diff --git a/drivers/cxl/fwctl.c b/drivers/cxl/fwctl.c
> index 85dee01d89d1..39c01ef4dbf2 100644
> --- a/drivers/cxl/fwctl.c
> +++ b/drivers/cxl/fwctl.c
> @@ -35,11 +35,207 @@ static void *cxlctl_info(struct fwctl_uctx *uctx, size_t *length)
> return info;
> }
>
> +static struct cxl_feat_entry *
> +get_support_feature_info(struct cxl_features_state *cxlfs,
> + const struct fwctl_rpc_cxl *rpc_in)
> +{
> + struct cxl_feat_entry *feat;
> + uuid_t uuid;
> +
> + if (rpc_in->op_size < sizeof(uuid))
> + return ERR_PTR(-EINVAL);
> +
> + if (copy_from_user(&uuid, u64_to_user_ptr(rpc_in->in_payload),
> + sizeof(uuid)))
> + return ERR_PTR(-EFAULT);
> +
> + for (int i = 0; i < cxlfs->num_features; i++) {
> + feat = &cxlfs->entries[i];
> + if (uuid_equal(&uuid, &feat->uuid))
> + return feat;
> + }
> +
> + return ERR_PTR(-EINVAL);
> +}
> +
> +static void *cxlctl_get_supported_features(struct cxl_features_state *cxlfs,
> + const struct fwctl_rpc_cxl *rpc_in,
> + size_t *out_len)
> +{
> + struct cxl_mbox_get_sup_feats_out *feat_out;
> + struct cxl_mbox_get_sup_feats_in feat_in;
> + struct cxl_feat_entry *pos;
> + size_t out_size;
> + int requested;
> + u32 count;
> + u16 start;
> + int i;
> +
> + if (rpc_in->op_size != sizeof(feat_in))
> + return ERR_PTR(-EINVAL);
> +
> + if (copy_from_user(&feat_in, u64_to_user_ptr(rpc_in->in_payload),
> + rpc_in->op_size))
> + return ERR_PTR(-EFAULT);
> +
> + count = le32_to_cpu(feat_in.count);
> + start = le16_to_cpu(feat_in.start_idx);
> + requested = count / sizeof(*pos);
> +
> + /*
> + * Make sure that the total requested number of entries is not greater
> + * than the total number of supported features allowed for userspace.
> + */
> + if (start >= cxlfs->num_user_features)
> + return ERR_PTR(-EINVAL);
> +
> + requested = min_t(int, requested, cxlfs->num_user_features - start);
> +
> + out_size = sizeof(struct fwctl_rpc_cxl_out) +
> + struct_size(feat_out, ents, requested);
> +
> + struct fwctl_rpc_cxl_out *rpc_out __free(kvfree) =
> + kvzalloc(out_size, GFP_KERNEL);
> + if (!rpc_out)
> + return ERR_PTR(-ENOMEM);
> +
> + rpc_out->size = struct_size(feat_out, ents, requested);
> + feat_out = (struct cxl_mbox_get_sup_feats_out *)rpc_out->payload;
> + if (requested == 0) {
> + feat_out->num_entries = cpu_to_le16(requested);
> + feat_out->supported_feats =
> + cpu_to_le16(cxlfs->num_user_features);
> + rpc_out->retval = CXL_MBOX_CMD_RC_SUCCESS;
> + *out_len = out_size;
> + return no_free_ptr(rpc_out);
> + }
> +
> + for (i = 0, pos = &feat_out->ents[0];
> + i < cxlfs->num_features; i++, pos++) {
> + if (i == requested)
> + break;
> +
> + memcpy(pos, &cxlfs->entries[i], sizeof(*pos));
> + /*
> + * If the feature is exclusive, set the set_feat_size to 0 to
> + * indicate that the feature is not changeable.
> + */
> + if (is_cxl_feature_exclusive(pos))
> + pos->set_feat_size = 0;
> + }
> +
> + feat_out->num_entries = cpu_to_le16(requested);
> + feat_out->supported_feats = cpu_to_le16(cxlfs->num_features);
> + rpc_out->retval = CXL_MBOX_CMD_RC_SUCCESS;
> + *out_len = out_size;
> +
> + return no_free_ptr(rpc_out);
> +}
> +
> +static bool cxlctl_validate_set_features(struct cxl_features_state *cxlfs,
> + const struct fwctl_rpc_cxl *rpc_in,
> + enum fwctl_rpc_scope scope)
> +{
> + struct cxl_feat_entry *feat;
> + u16 effects, mask;
> + u32 flags;
> +
> + feat = get_support_feature_info(cxlfs, rpc_in);
> + if (IS_ERR(feat))
> + return false;
> +
> + /* Ensure that the attribute is changeable */
> + flags = le32_to_cpu(feat->flags);
> + if (!(flags & CXL_FEATURE_F_CHANGEABLE))
> + return false;
> +
> + effects = le16_to_cpu(feat->effects);
> +
> + /*
> + * Reserved bits are set, rejecting since the effects is not
> + * comprehended by the driver.
> + */
> + if (effects & CXL_CMD_EFFECTS_RESERVED) {
> + dev_warn_once(&cxlfs->cxlmd->dev,
> + "Reserved bits set in the Feature effects field!\n");
> + return false;
> + }
> +
> + /* Currently no user background command support */
> + if (effects & CXL_CMD_BACKGROUND)
> + return false;
> +
> + /* Effects cause immediate change, highest security scope is needed */
> + mask = CXL_CMD_CONFIG_CHANGE_IMMEDIATE |
> + CXL_CMD_DATA_CHANGE_IMMEDIATE |
> + CXL_CMD_POLICY_CHANGE_IMMEDIATE |
> + CXL_CMD_LOG_CHANGE_IMMEDIATE;
> + if (effects & mask && scope >= FWCTL_RPC_DEBUG_WRITE_FULL)
> + return true;
> +
> + /* These effects supported for all WRITE scope */
> + if ((effects & CXL_CMD_CONFIG_CHANGE_COLD_RESET ||
> + effects & CXL_CMD_CONFIG_CHANGE_CONV_RESET ||
> + effects & CXL_CMD_CONFIG_CHANGE_CXL_RESET) &&
> + scope >= FWCTL_RPC_DEBUG_WRITE)
> + return true;
Jonathan and I came to the realization that bit[0,9:11] do not matter
because if they are not set there is no effect, and if they are set the
write is still allowed because the effect is post-reset.
The safety check that can be added is that if a Set has no immediate nor
post-reset effect then it is probably a device bug. In that case err on
the side of caution. I.e. all Set Feature must have at least one
immediate or reset effect.
next prev parent reply other threads:[~2025-02-05 1:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 22:03 [PATCH v3 00/16] cxl: Add CXL feature commands support via fwctl Dave Jiang
2025-02-04 22:03 ` [PATCH v3 01/16] cxl: Refactor user ioctl command path from mds to mailbox Dave Jiang
2025-02-05 17:41 ` Jonathan Cameron
2025-02-05 17:52 ` Dave Jiang
2025-02-07 5:47 ` Li Ming
2025-02-04 22:03 ` [PATCH v3 02/16] cxl: Enumerate feature commands Dave Jiang
2025-02-04 23:34 ` Dan Williams
2025-02-04 22:03 ` [PATCH v3 03/16] cxl: Add Get Supported Features command for kernel usage Dave Jiang
2025-02-04 23:50 ` Dan Williams
2025-02-07 5:42 ` Li Ming
2025-02-08 0:03 ` Dave Jiang
2025-02-04 22:03 ` [PATCH v3 04/16] cxl/test: Add Get Supported Features mailbox command support Dave Jiang
2025-02-07 5:51 ` Li Ming
2025-02-04 22:03 ` [PATCH v3 05/16] cxl/mbox: Add GET_FEATURE mailbox command Dave Jiang
2025-02-05 0:54 ` Dan Williams
2025-02-05 17:57 ` Jonathan Cameron
2025-02-05 23:12 ` Dan Williams
2025-02-06 11:03 ` Jonathan Cameron
2025-02-07 20:18 ` Dan Williams
2025-02-07 6:18 ` Li Ming
2025-02-04 22:03 ` [PATCH v3 06/16] cxl/mbox: Add SET_FEATURE " Dave Jiang
2025-02-04 22:03 ` [PATCH v3 07/16] cxl: Setup exclusive CXL features that are reserved for the kernel Dave Jiang
2025-02-04 22:03 ` [PATCH v3 08/16] cxl: Add FWCTL support to the CXL memdev driver Dave Jiang
2025-02-05 1:18 ` Dan Williams
2025-02-04 22:03 ` [PATCH v3 09/16] cxl: Add support for FWCTL get driver information callback Dave Jiang
2025-02-05 1:27 ` Dan Williams
2025-02-04 22:03 ` [PATCH v3 10/16] cxl: Move cxl feature command structs to user header Dave Jiang
2025-02-04 22:03 ` [PATCH v3 11/16] cxl: Add support for fwctl RPC command to enable CXL feature commands Dave Jiang
2025-02-05 1:41 ` Dan Williams [this message]
2025-02-04 22:03 ` [PATCH v3 12/16] cxl: Add support to handle user feature commands for get feature Dave Jiang
2025-02-04 22:03 ` [PATCH v3 13/16] cxl: Add support to handle user feature commands for set feature Dave Jiang
2025-02-04 22:03 ` [PATCH v3 14/16] cxl/test: Add Get Feature support to cxl_test Dave Jiang
2025-02-04 22:03 ` [PATCH v3 15/16] cxl/test: Add Set " Dave Jiang
2025-02-04 22:03 ` [PATCH v3 16/16] fwctl/cxl: Add documentation to FWCTL CXL Dave Jiang
2025-02-05 1:50 ` 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=67a2c1b1ee289_2d2c2941e@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@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