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>, <saeed@kernel.org>
Subject: Re: [PATCH v6 09/14] cxl: Add support for fwctl RPC command to enable CXL feature commands
Date: Wed, 19 Feb 2025 17:53:12 +0000 [thread overview]
Message-ID: <20250219175312.000070ec@huawei.com> (raw)
In-Reply-To: <20250218225721.2682235-10-dave.jiang@intel.com>
On Tue, 18 Feb 2025 15:54:38 -0700
Dave Jiang <dave.jiang@intel.com> 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. The flag
> field of the Feature details will be cleared of the "Changeable"
> field and the "set feat size" will be set to 0 to indicate that
> the feature is not changeable.
>
> Reviewed-by: Dan Williams <dan.j.williams@intel.com>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Hi Dave,
I'm probably missing something but I don't understand the need for
__DECLARE_FLEXIBLE_ARRAY() in the unions. We always seem to use one of
the structs (some of which have trailing flexible arrays).
> ---
> v6:
> - Embed hw op in 'fwctl_rpc_cxl'. (Saeed, Jason)
> - Move set_features bits to set_features enabling patch. (Saeed)
> - Fix copyright years. (Jason)
> ---
> drivers/cxl/core/features.c | 121 +++++++++++++++++++++++++++++++++++-
> include/uapi/cxl/features.h | 1 +
> include/uapi/fwctl/cxl.h | 57 +++++++++++++++++
> 3 files changed, 177 insertions(+), 2 deletions(-)
> create mode 100644 include/uapi/fwctl/cxl.h
>
> diff --git a/drivers/cxl/core/features.c b/drivers/cxl/core/features.c
> index 846de3294a5e..106ea9e25c82 100644
> --- a/drivers/cxl/core/features.c
> +++ b/drivers/cxl/core/features.c
> @@ -4,6 +4,7 @@
> #include <linux/device.h>
> #include <cxl/mailbox.h>
> #include <cxl/features.h>
> +#include <uapi/fwctl/cxl.h>
> #include "cxl.h"
> #include "core.h"
> #include "cxlmem.h"
> @@ -349,11 +350,127 @@ static void cxlctl_close_uctx(struct fwctl_uctx *uctx)
> {
> }
>
> +static void *cxlctl_get_supported_features(struct cxl_features_state *cxlfs,
> + const struct fwctl_rpc_cxl *rpc_in,
> + size_t *out_len)
> +{
> + const struct cxl_mbox_get_sup_feats_in *feat_in;
> + struct cxl_mbox_get_sup_feats_out *feat_out;
> + 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);
> +
> + feat_in = &rpc_in->get_sup_feats_in;
> + 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->entries->num_features)
> + return ERR_PTR(-EINVAL);
> +
> + requested = min_t(int, requested, cxlfs->entries->num_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;
Why not,
feat_out = rpc_out->get_sup_feats_out;
?
> + if (requested == 0) {
> + feat_out->num_entries = cpu_to_le16(requested);
> + feat_out->supported_feats =
> + cpu_to_le16(cxlfs->entries->num_features);
> + rpc_out->retval = CXL_MBOX_CMD_RC_SUCCESS;
> + *out_len = out_size;
> + return no_free_ptr(rpc_out);
> + }
> +
> + for (i = start, pos = &feat_out->ents[0];
> + i < cxlfs->entries->num_features; i++, pos++) {
> + if (i - start == requested)
> + break;
> +
> + memcpy(pos, &cxlfs->entries->ent[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)) {
> + u32 flags;
> +
> + pos->set_feat_size = 0;
> + flags = le32_to_cpu(pos->flags);
> + flags &= ~CXL_FEATURE_F_CHANGEABLE;
> + pos->flags = cpu_to_le32(flags);
> + }
> + }
> +
> + feat_out->num_entries = cpu_to_le16(requested);
> + feat_out->supported_feats = cpu_to_le16(cxlfs->entries->num_features);
> + rpc_out->retval = CXL_MBOX_CMD_RC_SUCCESS;
> + *out_len = out_size;
> +
> + return no_free_ptr(rpc_out);
> +}
> diff --git a/include/uapi/fwctl/cxl.h b/include/uapi/fwctl/cxl.h
> new file mode 100644
> index 000000000000..39996ec56816
> --- /dev/null
> +++ b/include/uapi/fwctl/cxl.h
> @@ -0,0 +1,57 @@
> +/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
> +/*
> + * Copyright (c) 2024-2025 Intel Corporation
> + *
> + * These are definitions for the mailbox command interface of CXL subsystem.
> + */
> +#ifndef _UAPI_FWCTL_CXL_H_
> +#define _UAPI_FWCTL_CXL_H_
> +
> +#include <linux/types.h>
> +#include <linux/stddef.h>
> +#include <cxl/features.h>
> +
> +struct cxl_mbox_get_sup_feats_in;
> +struct cxl_mbox_get_sup_feats_out;
These are defined now in uapi/cxl/features.h anyway so why is forwards
def needed?
> +
> +/**
> + * struct fwctl_rpc_cxl - ioctl(FWCTL_RPC) input for CXL
> + * @opcode: CXL mailbox command opcode
> + * @flags: Flags for the command (input).
> + * @op_size: Size of input payload.
> + * @reserved1: Reserved. Must be 0s.
> + * @get_sup_feats_in: Get Supported Features input
> + * @op: hardware operation input byte array
> + */
> +struct fwctl_rpc_cxl {
> + __struct_group(fwctl_rpc_cxl_hdr, hdr, /* no attrs */,
> + __u32 opcode;
> + __u32 flags;
> + __u32 op_size;
> + __u32 reserved1;
> + );
> + union {
> + struct cxl_mbox_get_sup_feats_in get_sup_feats_in;
> + __DECLARE_FLEX_ARRAY(__u8, op);
Similar to below. op isn't used in this patch that I can see.
Is it just here so it's obvious what op_size refers to?
> + };
> +};
> +
> +/**
> + * struct fwctl_rpc_cxl_out - ioctl(FWCTL_RPC) output for CXL
> + * @size: Size of the output payload
> + * @retval: Return value from device
> + * @get_sup_feats_out: Get Supported Features output
> + * @payload: Return data from device
> + */
> +struct fwctl_rpc_cxl_out {
> + __struct_group(fwctl_rpc_cxl_out_hdr, hdr, /* no attrs */,
> + __u32 size;
> + __u32 retval;
> + );
> + union {
> + struct cxl_mbox_get_sup_feats_out get_sup_feats_out;
> + __DECLARE_FLEX_ARRAY(__u8, payload);
I this patch I don't see a particular use for payload other
than where I've noted I think you can use get_sup_feats_out
directly.
> + };
> +};
> +
> +#endif
next prev parent reply other threads:[~2025-02-19 17:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 22:54 [PATCH v6 00/14] cxl: Add CXL feature commands support via fwctl Dave Jiang
2025-02-18 22:54 ` [PATCH v6 01/14] cxl: Enumerate feature commands Dave Jiang
2025-02-20 15:37 ` Shiju Jose
2025-02-18 22:54 ` [PATCH v6 02/14] cxl: Add Get Supported Features command for kernel usage Dave Jiang
2025-02-20 15:37 ` Shiju Jose
2025-02-18 22:54 ` [PATCH v6 03/14] cxl/test: Add Get Supported Features mailbox command support Dave Jiang
2025-02-18 22:54 ` [PATCH v6 04/14] cxl/mbox: Add GET_FEATURE mailbox command Dave Jiang
2025-02-18 22:54 ` [PATCH v6 05/14] cxl/mbox: Add SET_FEATURE " Dave Jiang
2025-02-18 22:54 ` [PATCH v6 06/14] cxl: Setup exclusive CXL features that are reserved for the kernel Dave Jiang
2025-02-20 15:37 ` Shiju Jose
2025-02-18 22:54 ` [PATCH v6 07/14] cxl: Add FWCTL support to CXL Dave Jiang
2025-02-19 7:25 ` Li Ming
2025-02-19 17:09 ` Jonathan Cameron
2025-02-18 22:54 ` [PATCH v6 08/14] cxl: Move cxl feature command structs to user header Dave Jiang
2025-02-19 7:26 ` Li Ming
2025-02-18 22:54 ` [PATCH v6 09/14] cxl: Add support for fwctl RPC command to enable CXL feature commands Dave Jiang
2025-02-19 7:27 ` Li Ming
2025-02-19 17:53 ` Jonathan Cameron [this message]
2025-02-19 17:56 ` Jason Gunthorpe
2025-02-19 18:00 ` Dave Jiang
2025-02-19 18:29 ` Dave Jiang
2025-02-18 22:54 ` [PATCH v6 10/14] cxl: Add support to handle user feature commands for get feature Dave Jiang
2025-02-19 17:57 ` Jonathan Cameron
2025-02-18 22:54 ` [PATCH v6 11/14] cxl: Add support to handle user feature commands for set feature Dave Jiang
2025-02-19 18:12 ` Jonathan Cameron
2025-02-19 18:31 ` Dave Jiang
2025-02-18 22:54 ` [PATCH v6 12/14] cxl/test: Add Get Feature support to cxl_test Dave Jiang
2025-02-18 22:54 ` [PATCH v6 13/14] cxl/test: Add Set " Dave Jiang
2025-02-18 22:54 ` [PATCH v6 14/14] 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=20250219175312.000070ec@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=saeed@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.