Linux CXL
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: alison.schofield@intel.com,
	Dan Williams <dan.j.williams@intel.com>,
	Ira Weiny <ira.weiny@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Ben Widawsky <bwidawsk@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Cc: linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v10 6/6] tools/testing/cxl: Mock support for Get Poison List
Date: Thu, 30 Mar 2023 16:42:56 -0700	[thread overview]
Message-ID: <627a4359-cac4-bef9-9033-ea782f47cbc7@intel.com> (raw)
In-Reply-To: <bac0ec2f8afdb0c28790b1595af49ac6fada0672.1679448904.git.alison.schofield@intel.com>



On 3/21/23 7:12 PM, alison.schofield@intel.com wrote:
> From: Alison Schofield <alison.schofield@intel.com>
> 
> Make mock memdevs support the Get Poison List mailbox command.
> Return a fake poison error record when the get poison list command
> is issued.
> 
> This supports testing the kernel tracing and cxl list capabilities
> for media errors.
> 
> Signed-off-by: Alison Schofield <alison.schofield@intel.com>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Reviewed-by: Ira Weiny <ira.weiny@intel.com>

Reviewed-by: Dave Jiang <dave.jiang@intel.com>

> ---
>   tools/testing/cxl/test/mem.c | 42 ++++++++++++++++++++++++++++++++++++
>   1 file changed, 42 insertions(+)
> 
> diff --git a/tools/testing/cxl/test/mem.c b/tools/testing/cxl/test/mem.c
> index 9263b04d35f7..2fa9c18d4c2c 100644
> --- a/tools/testing/cxl/test/mem.c
> +++ b/tools/testing/cxl/test/mem.c
> @@ -7,6 +7,7 @@
>   #include <linux/delay.h>
>   #include <linux/sizes.h>
>   #include <linux/bits.h>
> +#include <asm/unaligned.h>
>   #include <cxlmem.h>
>   
>   #include "trace.h"
> @@ -40,6 +41,10 @@ static struct cxl_cel_entry mock_cel[] = {
>   		.opcode = cpu_to_le16(CXL_MBOX_OP_GET_HEALTH_INFO),
>   		.effect = cpu_to_le16(0),
>   	},
> +	{
> +		.opcode = cpu_to_le16(CXL_MBOX_OP_GET_POISON),
> +		.effect = cpu_to_le16(0),
> +	},
>   };
>   
>   /* See CXL 2.0 Table 181 Get Health Info Output Payload */
> @@ -471,6 +476,8 @@ static int mock_id(struct cxl_dev_state *cxlds, struct cxl_mbox_cmd *cmd)
>   			cpu_to_le64(DEV_SIZE / CXL_CAPACITY_MULTIPLIER),
>   	};
>   
> +	put_unaligned_le24(CXL_POISON_LIST_MAX, id.poison_list_max_mer);
> +
>   	if (cmd->size_out < sizeof(id))
>   		return -EINVAL;
>   
> @@ -888,6 +895,34 @@ static int mock_health_info(struct cxl_dev_state *cxlds,
>   	return 0;
>   }
>   
> +static int mock_get_poison(struct cxl_dev_state *cxlds,
> +			   struct cxl_mbox_cmd *cmd)
> +{
> +	struct cxl_mbox_poison_payload_in *pi = cmd->payload_in;
> +
> +	/* Mock one poison record at pi.offset for 64 bytes */
> +	struct {
> +		struct cxl_mbox_poison_payload_out po;
> +		struct cxl_poison_record record;
> +	} __packed mock_plist = {
> +		.po = {
> +			.count = cpu_to_le16(1),
> +		},
> +		.record = {
> +			.length = cpu_to_le32(1),
> +			.address = cpu_to_le64(le64_to_cpu(pi->offset) +
> +					       CXL_POISON_SOURCE_INJECTED),
> +		},
> +	};
> +
> +	if (cmd->size_out < sizeof(mock_plist))
> +		return -EINVAL;
> +
> +	memcpy(cmd->payload_out, &mock_plist, sizeof(mock_plist));
> +	cmd->size_out = sizeof(mock_plist);
> +	return 0;
> +}
> +
>   static int cxl_mock_mbox_send(struct cxl_dev_state *cxlds, struct cxl_mbox_cmd *cmd)
>   {
>   	struct device *dev = cxlds->dev;
> @@ -942,6 +977,9 @@ static int cxl_mock_mbox_send(struct cxl_dev_state *cxlds, struct cxl_mbox_cmd *
>   	case CXL_MBOX_OP_PASSPHRASE_SECURE_ERASE:
>   		rc = mock_passphrase_secure_erase(cxlds, cmd);
>   		break;
> +	case CXL_MBOX_OP_GET_POISON:
> +		rc = mock_get_poison(cxlds, cmd);
> +		break;
>   	default:
>   		break;
>   	}
> @@ -1010,6 +1048,10 @@ static int cxl_mock_mem_probe(struct platform_device *pdev)
>   	if (rc)
>   		return rc;
>   
> +	rc = cxl_poison_state_init(cxlds);
> +	if (rc)
> +		return rc;
> +
>   	rc = cxl_dev_state_identify(cxlds);
>   	if (rc)
>   		return rc;

      reply	other threads:[~2023-03-30 23:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22  2:12 [PATCH v10 0/6] CXL Poison List Retrieval & Tracing alison.schofield
2023-03-22  2:12 ` [PATCH v10 1/6] cxl/mbox: Add GET_POISON_LIST mailbox command alison.schofield
2023-03-30 22:43   ` Dave Jiang
2023-03-31 15:41     ` Alison Schofield
2023-03-22  2:12 ` [PATCH v10 2/6] cxl/trace: Add TRACE support for CXL media-error records alison.schofield
2023-03-22  2:12 ` [PATCH v10 3/6] cxl/memdev: Add trigger_poison_list sysfs attribute alison.schofield
2023-03-30 22:55   ` Dave Jiang
2023-03-31 15:45     ` Alison Schofield
2023-03-22  2:12 ` [PATCH v10 4/6] cxl/region: Provide region info to the cxl_poison trace event alison.schofield
2023-03-30 23:41   ` Dave Jiang
2023-03-22  2:12 ` [PATCH v10 5/6] cxl/trace: Add an HPA to cxl_poison trace events alison.schofield
2023-03-22  2:12 ` [PATCH v10 6/6] tools/testing/cxl: Mock support for Get Poison List alison.schofield
2023-03-30 23:42   ` Dave Jiang [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=627a4359-cac4-bef9-9033-ea782f47cbc7@intel.com \
    --to=dave.jiang@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=alison.schofield@intel.com \
    --cc=bwidawsk@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --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