From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Vishal Verma <vishal.l.verma@intel.com>
Cc: Alison Schofield <alison.schofield@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Ben Widawsky <bwidawsk@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
<linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Russ Weight <russell.h.weight@intel.com>
Subject: Re: [PATCH v2 3/4] tools/testing/cxl: Use named effects for the Command Effect Log
Date: Thu, 8 Jun 2023 14:31:53 +0100 [thread overview]
Message-ID: <20230608143153.00007ae1@Huawei.com> (raw)
In-Reply-To: <20230602-vv-fw_update-v2-3-e9e5cd5adb44@intel.com>
On Mon, 05 Jun 2023 14:20:24 -0600
Vishal Verma <vishal.l.verma@intel.com> wrote:
> As more emulated mailbox commands are added to cxl_test, it is a pain
> point to look up command effect numbers for each effect. Replace the
> bare numbers in the mock driver with an enum that lists all possible
> effects.
>
> Suggested-by: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
> Cc: Davidlohr Bueso <dave@stgolabs.net>
> Cc: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
> Cc: Russ Weight <russell.h.weight@intel.com>
> Cc: Alison Schofield <alison.schofield@intel.com>
> Cc: Ira Weiny <ira.weiny@intel.com>
> Cc: Dave Jiang <dave.jiang@intel.com>
> Cc: Ben Widawsky <bwidawsk@kernel.org>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
LGTM
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
> tools/testing/cxl/test/mem.c | 32 +++++++++++++++++++++++---------
> 1 file changed, 23 insertions(+), 9 deletions(-)
>
> diff --git a/tools/testing/cxl/test/mem.c b/tools/testing/cxl/test/mem.c
> index 403cd3608772..68668d8df1cd 100644
> --- a/tools/testing/cxl/test/mem.c
> +++ b/tools/testing/cxl/test/mem.c
> @@ -21,42 +21,56 @@
>
> static unsigned int poison_inject_dev_max = MOCK_INJECT_DEV_MAX;
>
> +enum cxl_command_effects {
> + CONF_CHANGE_COLD_RESET = 0,
> + CONF_CHANGE_IMMEDIATE,
> + DATA_CHANGE_IMMEDIATE,
> + POLICY_CHANGE_IMMEDIATE,
> + LOG_CHANGE_IMMEDIATE,
> + SECURITY_CHANGE_IMMEDIATE,
> + BACKGROUND_OP,
> + SECONDARY_MBOX_SUPPORTED,
> +};
> +
> +#define CXL_CMD_EFFECT_NONE cpu_to_le16(0)
> +
> static struct cxl_cel_entry mock_cel[] = {
> {
> .opcode = cpu_to_le16(CXL_MBOX_OP_GET_SUPPORTED_LOGS),
> - .effect = cpu_to_le16(0),
> + .effect = CXL_CMD_EFFECT_NONE,
> },
> {
> .opcode = cpu_to_le16(CXL_MBOX_OP_IDENTIFY),
> - .effect = cpu_to_le16(0),
> + .effect = CXL_CMD_EFFECT_NONE,
> },
> {
> .opcode = cpu_to_le16(CXL_MBOX_OP_GET_LSA),
> - .effect = cpu_to_le16(0),
> + .effect = CXL_CMD_EFFECT_NONE,
> },
> {
> .opcode = cpu_to_le16(CXL_MBOX_OP_GET_PARTITION_INFO),
> - .effect = cpu_to_le16(0),
> + .effect = CXL_CMD_EFFECT_NONE,
> },
> {
> .opcode = cpu_to_le16(CXL_MBOX_OP_SET_LSA),
> - .effect = cpu_to_le16(EFFECT(1) | EFFECT(2)),
> + .effect = cpu_to_le16(EFFECT(CONF_CHANGE_IMMEDIATE) |
> + EFFECT(DATA_CHANGE_IMMEDIATE)),
> },
> {
> .opcode = cpu_to_le16(CXL_MBOX_OP_GET_HEALTH_INFO),
> - .effect = cpu_to_le16(0),
> + .effect = CXL_CMD_EFFECT_NONE,
> },
> {
> .opcode = cpu_to_le16(CXL_MBOX_OP_GET_POISON),
> - .effect = cpu_to_le16(0),
> + .effect = CXL_CMD_EFFECT_NONE,
> },
> {
> .opcode = cpu_to_le16(CXL_MBOX_OP_INJECT_POISON),
> - .effect = cpu_to_le16(EFFECT(2)),
> + .effect = cpu_to_le16(EFFECT(DATA_CHANGE_IMMEDIATE)),
> },
> {
> .opcode = cpu_to_le16(CXL_MBOX_OP_CLEAR_POISON),
> - .effect = cpu_to_le16(EFFECT(2)),
> + .effect = cpu_to_le16(EFFECT(DATA_CHANGE_IMMEDIATE)),
> },
> };
>
>
next prev parent reply other threads:[~2023-06-08 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 20:20 [PATCH v2 0/4] cxl: Add a firmware update mechanism and cxl_test emulation Vishal Verma
2023-06-05 20:20 ` [PATCH v2 1/4] cxl: add a firmware update mechanism using the sysfs firmware loader Vishal Verma
2023-06-08 14:49 ` Jonathan Cameron
2023-06-08 20:15 ` Verma, Vishal L
2023-06-08 20:26 ` Verma, Vishal L
2023-06-09 11:08 ` Jonathan Cameron
2023-06-09 11:06 ` Jonathan Cameron
2023-06-05 20:20 ` [PATCH v2 2/4] tools/testing/cxl: Fix command effects for inject/clear poison Vishal Verma
2023-06-07 19:18 ` Alison Schofield
2023-06-08 11:01 ` Jonathan Cameron
2023-06-05 20:20 ` [PATCH v2 3/4] tools/testing/cxl: Use named effects for the Command Effect Log Vishal Verma
2023-06-07 19:19 ` Alison Schofield
2023-06-08 13:31 ` Jonathan Cameron [this message]
2023-06-05 20:20 ` [PATCH v2 4/4] tools/testing/cxl: add firmware update emulation to CXL memdevs Vishal Verma
2023-06-08 14:54 ` 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=20230608143153.00007ae1@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=russell.h.weight@intel.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;
as well as URLs for NNTP newsgroup(s).