From: Alison Schofield <alison.schofield@intel.com>
To: Dave Jiang <dave.jiang@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>,
Steven Rostedt <rostedt@goodmis.org>,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v10 3/6] cxl/memdev: Add trigger_poison_list sysfs attribute
Date: Fri, 31 Mar 2023 08:45:33 -0700 [thread overview]
Message-ID: <ZCcAHbnGu5c46Tg4@aschofie-mobl2> (raw)
In-Reply-To: <6e59a3d6-0b68-2d36-d25a-652167168db8@intel.com>
On Thu, Mar 30, 2023 at 03:55:46PM -0700, Dave Jiang wrote:
>
>
> On 3/21/23 7:12 PM, alison.schofield@intel.com wrote:
> > From: Alison Schofield <alison.schofield@intel.com>
> >
> > When a boolean 'true' is written to this attribute the memdev driver
> > retrieves the poison list from the device. The list consists of
> > addresses that are poisoned, or would result in poison if accessed,
> > and the source of the poison. This attribute is only visible for
> > devices supporting the capability. The retrieved errors are logged
> > as kernel trace events with the label 'cxl_poison'.
> >
> > 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>
> > ---
> > Documentation/ABI/testing/sysfs-bus-cxl | 14 ++++++++
> > drivers/cxl/core/memdev.c | 48 +++++++++++++++++++++++++
> > drivers/cxl/cxlmem.h | 5 ++-
> > drivers/cxl/mem.c | 36 +++++++++++++++++++
> > 4 files changed, 102 insertions(+), 1 deletion(-)
> >
snip
> > +static int cxl_get_poison_by_memdev(struct cxl_memdev *cxlmd)
> > +{
> > + struct cxl_dev_state *cxlds = cxlmd->cxlds;
> > + u64 offset, length;
> > + int rc = 0;
> > +
> > + /* CXL 3.0 Spec 8.2.9.8.4.1 Separate pmem and ram poison requests */
> > + if (resource_size(&cxlds->pmem_res)) {
> > + offset = cxlds->pmem_res.start;
> > + length = resource_size(&cxlds->pmem_res);
> > + rc = cxl_mem_get_poison(cxlmd, offset, length, NULL);
> > + if (rc)
> > + return rc;
> > + }
> > + if (resource_size(&cxlds->ram_res)) {
> > + offset = cxlds->ram_res.start;
> > + length = resource_size(&cxlds->ram_res);
> > + rc = cxl_mem_get_poison(cxlmd, offset, length, NULL);
> > + /*
> > + * Invalid Physical Address is not an error for
> > + * volatile addresses. Device support is optional.
> > + */
> > + if (rc == -EFAULT)
See this EFAULT. That is why I changed table further down to
allow EFAULT to get through explicitly.
snip
> > @@ -130,6 +177,7 @@ static umode_t cxl_memdev_visible(struct kobject *kobj, struct attribute *a,
> > {
> > if (!IS_ENABLED(CONFIG_NUMA) && a == &dev_attr_numa_node.attr)
> > return 0;
> > +
>
> Stray blank line?
Yes.
>
> > return a->mode;
> > }
> > diff --git a/drivers/cxl/cxlmem.h b/drivers/cxl/cxlmem.h
> > index 57a5999ddb35..5febaa3f9b04 100644
> > --- a/drivers/cxl/cxlmem.h
> > +++ b/drivers/cxl/cxlmem.h
> > @@ -145,7 +145,7 @@ struct cxl_mbox_cmd {
> > C(FWROLLBACK, -ENXIO, "rolled back to the previous active FW"), \
> > C(FWRESET, -ENXIO, "FW failed to activate, needs cold reset"), \
> > C(HANDLE, -ENXIO, "one or more Event Record Handles were invalid"), \
> > - C(PADDR, -ENXIO, "physical address specified is invalid"), \
> > + C(PADDR, -EFAULT, "physical address specified is invalid"), \
>
> Seems unrelated change? Does it go with previous patch?
See prior note. Need this one explicitly.
>
snip to end.
next prev parent reply other threads:[~2023-03-31 15:45 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 [this message]
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
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=ZCcAHbnGu5c46Tg4@aschofie-mobl2 \
--to=alison.schofield@intel.com \
--cc=Jonathan.Cameron@huawei.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=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;
as well as URLs for NNTP newsgroup(s).