From: Dave Jiang <dave.jiang@intel.com>
To: <alison.schofield@intel.com>, Vishal Verma <vishal.l.verma@intel.com>
Cc: <nvdimm@lists.linux.dev>, <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v6 1/7] libcxl: add interfaces for GET_POISON_LIST mailbox commands
Date: Fri, 19 Jan 2024 11:32:07 -0700 [thread overview]
Message-ID: <694ad508-cc06-4e3a-974b-3d1403adeda9@intel.com> (raw)
In-Reply-To: <22d01bd1af9af5370d1e35094176dbd66ef20dac.1705534719.git.alison.schofield@intel.com>
On 1/17/24 17:28, alison.schofield@intel.com wrote:
> From: Alison Schofield <alison.schofield@intel.com>
>
> CXL devices maintain a list of locations that are poisoned or result
> in poison if the addresses are accessed by the host.
>
> Per the spec (CXL 3.1 8.2.9.9.4.1), the device returns the Poison
> List as a set of Media Error Records that include the source of the
> error, the starting device physical address and length.
>
> Trigger the retrieval of the poison list by writing to the memory
> device sysfs attribute: trigger_poison_list. The CXL driver only
> offers triggering per memdev, so the trigger by region interface
> offered here is a convenience API that triggers a poison list
> retrieval for each memdev contributing to a region.
>
> int cxl_memdev_trigger_poison_list(struct cxl_memdev *memdev);
> int cxl_region_trigger_poison_list(struct cxl_region *region);
>
> The resulting poison records are logged as kernel trace events
> named 'cxl_poison'.
>
> Signed-off-by: Alison Schofield <alison.schofield@intel.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> cxl/lib/libcxl.c | 47 ++++++++++++++++++++++++++++++++++++++++++++++
> cxl/lib/libcxl.sym | 6 ++++++
> cxl/libcxl.h | 2 ++
> 3 files changed, 55 insertions(+)
>
> diff --git a/cxl/lib/libcxl.c b/cxl/lib/libcxl.c
> index af4ca44eae19..cc95c2d7c94a 100644
> --- a/cxl/lib/libcxl.c
> +++ b/cxl/lib/libcxl.c
> @@ -1647,6 +1647,53 @@ CXL_EXPORT int cxl_memdev_disable_invalidate(struct cxl_memdev *memdev)
> return 0;
> }
>
> +CXL_EXPORT int cxl_memdev_trigger_poison_list(struct cxl_memdev *memdev)
> +{
> + struct cxl_ctx *ctx = cxl_memdev_get_ctx(memdev);
> + char *path = memdev->dev_buf;
> + int len = memdev->buf_len, rc;
> +
> + if (snprintf(path, len, "%s/trigger_poison_list",
> + memdev->dev_path) >= len) {
> + err(ctx, "%s: buffer too small\n",
> + cxl_memdev_get_devname(memdev));
> + return -ENXIO;
> + }
> + rc = sysfs_write_attr(ctx, path, "1\n");
> + if (rc < 0) {
> + fprintf(stderr,
> + "%s: Failed write sysfs attr trigger_poison_list\n",
> + cxl_memdev_get_devname(memdev));
> + return rc;
> + }
> + return 0;
> +}
> +
> +CXL_EXPORT int cxl_region_trigger_poison_list(struct cxl_region *region)
> +{
> + struct cxl_memdev_mapping *mapping;
> + int rc;
> +
> + cxl_mapping_foreach(region, mapping) {
> + struct cxl_decoder *decoder;
> + struct cxl_memdev *memdev;
> +
> + decoder = cxl_mapping_get_decoder(mapping);
> + if (!decoder)
> + continue;
> +
> + memdev = cxl_decoder_get_memdev(decoder);
> + if (!memdev)
> + continue;
> +
> + rc = cxl_memdev_trigger_poison_list(memdev);
> + if (rc)
> + return rc;
> + }
> +
> + return 0;
> +}
> +
> CXL_EXPORT int cxl_memdev_enable(struct cxl_memdev *memdev)
> {
> struct cxl_ctx *ctx = cxl_memdev_get_ctx(memdev);
> diff --git a/cxl/lib/libcxl.sym b/cxl/lib/libcxl.sym
> index 8fa1cca3d0d7..277b7e21d6a6 100644
> --- a/cxl/lib/libcxl.sym
> +++ b/cxl/lib/libcxl.sym
> @@ -264,3 +264,9 @@ global:
> cxl_memdev_update_fw;
> cxl_memdev_cancel_fw_update;
> } LIBCXL_5;
> +
> +LIBCXL_7 {
> +global:
> + cxl_memdev_trigger_poison_list;
> + cxl_region_trigger_poison_list;
> +} LIBCXL_6;
> diff --git a/cxl/libcxl.h b/cxl/libcxl.h
> index 0f4f4b2648fb..ecdffe36df2c 100644
> --- a/cxl/libcxl.h
> +++ b/cxl/libcxl.h
> @@ -460,6 +460,8 @@ enum cxl_setpartition_mode {
>
> int cxl_cmd_partition_set_mode(struct cxl_cmd *cmd,
> enum cxl_setpartition_mode mode);
> +int cxl_memdev_trigger_poison_list(struct cxl_memdev *memdev);
> +int cxl_region_trigger_poison_list(struct cxl_region *region);
>
> #ifdef __cplusplus
> } /* extern "C" */
next prev parent reply other threads:[~2024-01-19 18:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 0:27 [ndctl PATCH v6 0/7] Support poison list retrieval alison.schofield
2024-01-18 0:28 ` [PATCH v6 1/7] libcxl: add interfaces for GET_POISON_LIST mailbox commands alison.schofield
2024-01-19 18:32 ` Dave Jiang [this message]
2024-01-18 0:28 ` [PATCH v6 2/7] cxl: add an optional pid check to event parsing alison.schofield
2024-01-19 18:35 ` Dave Jiang
2024-01-18 0:28 ` [PATCH v6 3/7] cxl/event_trace: add a private context for private parsers alison.schofield
2024-01-19 21:08 ` Dave Jiang
2024-01-18 0:28 ` [PATCH v6 4/7] cxl/event_trace: add helpers get_field_[string|data]() alison.schofield
2024-01-19 21:18 ` Dave Jiang
2024-01-18 0:28 ` [PATCH v6 5/7] cxl/list: collect and parse media_error records alison.schofield
2024-01-18 0:28 ` [PATCH v6 6/7] cxl/list: add --media-errors option to cxl list alison.schofield
2024-01-18 0:28 ` [PATCH v6 7/7] cxl/test: add cxl-poison.sh unit test alison.schofield
2024-01-18 21:56 ` [ndctl PATCH v6 0/7] Support poison list retrieval Dan Williams
2024-01-18 23:34 ` Alison Schofield
2024-01-18 23:55 ` Dan Williams
2024-02-07 22:54 ` Alison Schofield
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=694ad508-cc06-4e3a-974b-3d1403adeda9@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--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