From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: <alison.schofield@intel.com>
Cc: 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>,
Dave Jiang <dave.jiang@intel.com>, <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v5 03/12] cxl/memdev: Warn of poison inject or clear to a mapped region
Date: Thu, 30 Mar 2023 19:55:46 +0100 [thread overview]
Message-ID: <20230330195546.00004774@Huawei.com> (raw)
In-Reply-To: <fc7db7de4778803a3221d7fd5a203bf971fdac61.1679892337.git.alison.schofield@intel.com>
On Sun, 26 Mar 2023 22:03:09 -0700
alison.schofield@intel.com wrote:
> From: Alison Schofield <alison.schofield@intel.com>
>
> Inject and clear poison capabilities and intended for debug usage only.
> In order to be useful in debug environments, the driver needs to allow
> inject and clear operations on DPAs mapped in regions.
>
> dev_warn_once() when either operation occurs.
>
> Signed-off-by: Alison Schofield <alison.schofield@intel.com>
> ---
> drivers/cxl/core/memdev.c | 59 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 59 insertions(+)
>
> diff --git a/drivers/cxl/core/memdev.c b/drivers/cxl/core/memdev.c
> index 0e39c3c3fb09..a83619c31f61 100644
> --- a/drivers/cxl/core/memdev.c
> +++ b/drivers/cxl/core/memdev.c
> @@ -213,6 +213,50 @@ ssize_t cxl_trigger_poison_list(struct device *dev,
> }
> EXPORT_SYMBOL_NS_GPL(cxl_trigger_poison_list, CXL);
>
> +struct cxl_dpa_to_region_context {
> + struct cxl_region *cxlr;
> + u64 dpa;
> +};
> +
> +static int __cxl_dpa_to_region(struct device *dev, void *arg)
> +{
> + struct cxl_dpa_to_region_context *ctx = arg;
> + struct cxl_endpoint_decoder *cxled;
> + u64 dpa = ctx->dpa;
> +
> + if (!is_endpoint_decoder(dev))
> + return 0;
> +
> + cxled = to_cxl_endpoint_decoder(dev);
> + if (!cxled->dpa_res || !resource_size(cxled->dpa_res))
> + return 0;
> +
> + if (dpa > cxled->dpa_res->end || dpa < cxled->dpa_res->start)
> + return 0;
> +
> + dev_dbg(dev, "dpa:0x%llx mapped in region:%s\n", dpa,
> + dev_name(&cxled->cxld.region->dev));
> +
> + ctx->cxlr = cxled->cxld.region;
> +
If we have a match, little point in letting walk continue.
return 1;
Also, I "think" we just know that the association has been built.
Injecting poison is probably still fine if the region / decoder hasn't yet
been committed.
Jonathan
> + return 0;
> +}
> +
> +static struct cxl_region *cxl_dpa_to_region(struct cxl_memdev *cxlmd, u64 dpa)
> +{
> + struct cxl_dpa_to_region_context ctx;
> + struct cxl_port *port;
> +
> + ctx = (struct cxl_dpa_to_region_context) {
> + .dpa = dpa,
> + };
> + port = dev_get_drvdata(&cxlmd->dev);
> + if (port && is_cxl_endpoint(port) && port->commit_end != -1)
> + device_for_each_child(&port->dev, &ctx, __cxl_dpa_to_region);
> +
> + return ctx.cxlr;
> +}
> +
> static int cxl_validate_poison_dpa(struct cxl_memdev *cxlmd, u64 dpa)
> {
> struct cxl_dev_state *cxlds = cxlmd->cxlds;
> @@ -242,6 +286,7 @@ int cxl_inject_poison(struct device *dev, u64 dpa)
> struct cxl_memdev *cxlmd = to_cxl_memdev(dev);
> struct cxl_mbox_inject_poison inject;
> struct cxl_mbox_cmd mbox_cmd;
> + struct cxl_region *cxlr;
> int rc;
>
> if (!IS_ENABLED(CONFIG_DEBUG_FS))
> @@ -261,6 +306,13 @@ int cxl_inject_poison(struct device *dev, u64 dpa)
> .payload_in = &inject,
> };
> rc = cxl_internal_send_cmd(cxlmd->cxlds, &mbox_cmd);
> + if (rc)
> + goto out;
> +
> + cxlr = cxl_dpa_to_region(cxlmd, dpa);
> + if (cxlr)
> + dev_warn_once(dev, "poison inject dpa:0x%llx region: %s\n",
> + dpa, dev_name(&cxlr->dev));
> out:
> up_read(&cxl_dpa_rwsem);
>
> @@ -273,6 +325,7 @@ int cxl_clear_poison(struct device *dev, u64 dpa)
> struct cxl_memdev *cxlmd = to_cxl_memdev(dev);
> struct cxl_mbox_clear_poison clear;
> struct cxl_mbox_cmd mbox_cmd;
> + struct cxl_region *cxlr;
> int rc;
>
> if (!IS_ENABLED(CONFIG_DEBUG_FS))
> @@ -303,7 +356,13 @@ int cxl_clear_poison(struct device *dev, u64 dpa)
> };
>
> rc = cxl_internal_send_cmd(cxlmd->cxlds, &mbox_cmd);
> + if (rc)
> + goto out;
>
> + cxlr = cxl_dpa_to_region(cxlmd, dpa);
> + if (cxlr)
> + dev_warn_once(dev, "poison clear dpa:0x%llx region: %s\n",
> + dpa, dev_name(&cxlr->dev));
> out:
> up_read(&cxl_dpa_rwsem);
>
next prev parent reply other threads:[~2023-03-30 18:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 5:03 [PATCH v5 0/12] cxl: CXL Inject & Clear Poison alison.schofield
2023-03-27 5:03 ` [PATCH v5 01/12] cxl/memdev: Add support for the Inject Poison mailbox command alison.schofield
2023-03-30 18:47 ` Jonathan Cameron
2023-03-31 18:11 ` Dave Jiang
2023-03-31 18:52 ` Alison Schofield
2023-03-27 5:03 ` [PATCH v5 02/12] cxl/memdev: Add support for the Clear " alison.schofield
2023-03-30 18:50 ` Jonathan Cameron
2023-03-30 20:12 ` Alison Schofield
2023-04-03 14:08 ` Jonathan Cameron
2023-03-31 18:40 ` Dave Jiang
2023-03-31 19:55 ` Alison Schofield
2023-03-31 21:18 ` Dave Jiang
2023-03-27 5:03 ` [PATCH v5 03/12] cxl/memdev: Warn of poison inject or clear to a mapped region alison.schofield
2023-03-30 18:55 ` Jonathan Cameron [this message]
2023-04-11 17:43 ` Alison Schofield
2023-04-13 17:07 ` Jonathan Cameron
2023-03-27 5:03 ` [PATCH v5 04/12] cxl/memdev: Trace inject and clear poison as cxl_poison events alison.schofield
2023-03-30 19:03 ` Jonathan Cameron
2023-03-31 18:53 ` Dave Jiang
2023-03-27 5:03 ` [PATCH v5 05/12] cxl/mem: Add debugfs attributes for poison inject and clear alison.schofield
2023-03-30 18:58 ` Jonathan Cameron
2023-03-27 5:03 ` [PATCH v5 06/12] cxl/memdev: Make inject and clear poison cmds kernel exclusive alison.schofield
2023-03-31 19:10 ` Dave Jiang
2023-03-27 5:03 ` [PATCH v5 07/12] cxl/mbox: Block inject and clear poison opcodes in raw mode alison.schofield
2023-03-31 19:10 ` Dave Jiang
2023-03-27 5:03 ` [PATCH v5 08/12] tools/testing/cxl: Mock the Inject Poison mailbox command alison.schofield
2023-03-31 19:13 ` Dave Jiang
2023-03-27 5:03 ` [PATCH v5 09/12] tools/testing/cxl: Mock the Clear " alison.schofield
2023-03-31 19:15 ` Dave Jiang
2023-03-27 5:03 ` [PATCH v5 10/12] tools/testing/cxl: Use injected poison for get poison list alison.schofield
2023-03-31 19:16 ` Dave Jiang
2023-03-27 5:03 ` [PATCH v5 11/12] tools/testing/cxl: Add a sysfs attr to test poison inject limits alison.schofield
2023-03-31 19:18 ` Dave Jiang
2023-03-27 5:03 ` [PATCH v5 12/12] tools/testing/cxl: Require CONFIG_DEBUG_FS alison.schofield
2023-03-31 19:20 ` 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=20230330195546.00004774@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=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).