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 1/6] cxl/mbox: Add GET_POISON_LIST mailbox command
Date: Fri, 31 Mar 2023 08:41:42 -0700 [thread overview]
Message-ID: <ZCb/No9ksoqaAUBJ@aschofie-mobl2> (raw)
In-Reply-To: <ce9221f4-88da-e16c-8dfb-e3438159f5d1@intel.com>
On Thu, Mar 30, 2023 at 03:43:18PM -0700, Dave Jiang wrote:
>
>
> On 3/21/23 7:12 PM, 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.0 8.2.9.8.4.1), the device returns this Poison
>
> Maybe you need a comma here?
>
> > list as a set of Media Error Records that include the source of the
>
> extra space between "of" and "Media"
>
> > error, the starting device physical address and length. The length is
>
> Should add a comma before "and length".
>
> > the number of adjacent DPAs in the record and is in units of 64 bytes.
> >
> > Retrieve the poison list.
FYI - this is v10, but things you are pointing out do apply to v11.
I'll update the commit msg as you suggest.
> >
snip
> > +
> > +struct cxl_mbox_poison_payload_out {
> > + u8 flags;
> > + u8 rsvd1;
> > + __le64 overflow_t;
> > + __le16 count;
> > + u8 rsvd2[20];
> > + struct cxl_poison_record {
> > + __le64 address;
> > + __le32 length;
> > + __le32 rsvd;
> > + } __packed record[];
> > +} __packed;
>
> Pretty long struct name. poison_mbox_in and poison_mbox_out?
Yeah...I'll drop the _payload from each. Thanks!
>
snip to end.
next prev parent reply other threads:[~2023-03-31 15:41 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 [this message]
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
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=ZCb/No9ksoqaAUBJ@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