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 16/16] fwctl/cxl: Add documentation to FWCTL CXL
Date: Tue, 4 Feb 2025 17:50:14 -0800 [thread overview]
Message-ID: <67a2c3d64966b_2d2c2942e@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20250204220430.4146187-17-dave.jiang@intel.com>
Dave Jiang wrote:
> Add policy and operational documentation for FWCTL CXL.
>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> v3:
> - Add a sentence on how entries are filtered. (Jonathan)
> ---
> .../userspace-api/fwctl/fwctl-cxl.rst | 137 ++++++++++++++++++
> Documentation/userspace-api/fwctl/index.rst | 1 +
> MAINTAINERS | 1 +
> 3 files changed, 139 insertions(+)
> create mode 100644 Documentation/userspace-api/fwctl/fwctl-cxl.rst
>
> diff --git a/Documentation/userspace-api/fwctl/fwctl-cxl.rst b/Documentation/userspace-api/fwctl/fwctl-cxl.rst
> new file mode 100644
> index 000000000000..81c694f6a44d
> --- /dev/null
> +++ b/Documentation/userspace-api/fwctl/fwctl-cxl.rst
> @@ -0,0 +1,137 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +================
> +fwctl cxl driver
> +================
> +
> +:Author: Dave Jiang
[..]
Thanks for the verb tense changes!
> +
> +Code example of a Get Feature
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +.. code-block:: c
Nice, thanks for the example, it finally allows me to put a finger on a
naming nit below...
> +
> + static int cxl_fwctl_rpc_get_test_feature(int fd, struct test_feature *feat_ctx,
> + const uint32_t expected_data)
> + {
> + struct cxl_mbox_get_feat_in feat_in __attribute__((aligned(16))) = {0};
> + struct fwctl_rpc_cxl in __attribute__((aligned(16))) = {0};
> + struct fwctl_rpc_cxl_out *out;
> + struct fwctl_rpc rpc = {0};
> + size_t out_size;
> + uint32_t val;
> + void *data;
> + int rc;
> +
> + uuid_copy(feat_in.uuid, feat_ctx->uuid);
> + feat_in.count = feat_ctx->get_size;
> +
> + out_size = sizeof(*out) + feat_in.count;
> + out = aligned_alloc(16, out_size);
> + if (!out)
> + return -ENOMEM;
> +
> + memset(out, 0, out_size);
> + data = out->payload;
> +
> + in.command_id = CXL_FEATURE_ID_GET_FEATURE;
So this should probably be CXL_FWCTL_GET_FEATURE, right? There's no such
thing as a feature command id to userspace only FWCTL command ids that
translate to one of Get Suppported, Get, and Set Feature(s), and the
"id" is implied.
> + in.op_size = sizeof(feat_in);
> + in.in_payload = (uint64_t)(uint64_t *)&feat_in;
> +
> + rpc.size = sizeof(rpc);
> + rpc.scope = FWCTL_RPC_CONFIGURATION;
> + rpc.in_len = sizeof(in);
> + rpc.out_len = out_size;
> + rpc.in = (uint64_t)(uint64_t *)∈
> + rpc.out = (uint64_t)(uint64_t *)out;
> +
> + rc = send_command(fd, &rpc, out);
> + if (rc)
> + goto out;
> +
> + val = le32toh(*(__le32 *)data);
> + if (memcmp(&val, &expected_data, sizeof(val)) != 0) {
> + rc = -ENXIO;
> + goto out;
> + }
> +
> + out:
> + free(out);
> + return rc;
> + }
> +
> +It is recommended to take a look at CXL CLI test directory
Passive -> imperative:
s/It is recommended to take/Take/
Other than that, this looks good!
prev parent reply other threads:[~2025-02-05 1:51 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
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 [this message]
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=67a2c3d64966b_2d2c2942e@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