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>,
Dave Jiang <dave.jiang@intel.com>,
Ben Widawsky <bwidawsk@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>, <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v11 3/6] cxl/memdev: Add trigger_poison_list sysfs attribute
Date: Thu, 30 Mar 2023 18:42:40 +0100 [thread overview]
Message-ID: <20230330184240.0000411f@Huawei.com> (raw)
In-Reply-To: <f1a60cac8cc404f2fc8768333afbf16be01a5a90.1679888450.git.alison.schofield@intel.com>
On Sun, 26 Mar 2023 22:02:09 -0700
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>
A grumpy reviewer comment inline... But meh, if non else minds
let it be.
> static struct attribute *cxl_memdev_attributes[] = {
> &dev_attr_serial.attr,
> &dev_attr_firmware_version.attr,
> @@ -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;
> +
Noise...
> return a->mode;
> }
next prev parent reply other threads:[~2023-03-30 17:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 5:02 [PATCH v11 0/6] CXL Poison List Retrieval & Tracing alison.schofield
2023-03-27 5:02 ` [PATCH v11 1/6] cxl/mbox: Add GET_POISON_LIST mailbox command alison.schofield
2023-03-27 5:02 ` [PATCH v11 2/6] cxl/trace: Add TRACE support for CXL media-error records alison.schofield
2023-03-29 20:44 ` Ira Weiny
2023-03-27 5:02 ` [PATCH v11 3/6] cxl/memdev: Add trigger_poison_list sysfs attribute alison.schofield
2023-03-30 17:42 ` Jonathan Cameron [this message]
2023-03-30 20:20 ` Alison Schofield
2023-03-27 5:02 ` [PATCH v11 4/6] cxl/region: Provide region info to the cxl_poison trace event alison.schofield
2023-03-29 20:43 ` Ira Weiny
2023-03-31 15:52 ` Alison Schofield
2023-03-27 5:02 ` [PATCH v11 5/6] cxl/trace: Add an HPA to cxl_poison trace events alison.schofield
2023-03-27 5:02 ` [PATCH v11 6/6] tools/testing/cxl: Mock support for Get Poison List alison.schofield
2023-03-30 17:45 ` [PATCH v11 0/6] CXL Poison List Retrieval & Tracing 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=20230330184240.0000411f@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=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