From: Richard Cheng <icheng@nvidia.com>
To: Gaobin Huang <huanggaobin23@semi.ac.cn>
Cc: linux-cxl@vger.kernel.org, Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jic23@kernel.org>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dan Williams <djbw@kernel.org>, Ira Weiny <iweiny@kernel.org>,
Li Ming <ming.li@zohomail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cxl/mbox: Add the CXL 4.0 command return codes 001Fh and 0020h
Date: Thu, 15 Oct 2026 16:16:56 +0800 [thread overview]
Message-ID: <atCLjvE5xJp9jo6L@MWDK4CY14F> (raw)
In-Reply-To: <20261015055048.1765042-1-huanggaobin23@semi.ac.cn>
On Thu, Oct 15, 2026 at 01:50:48PM +0800, Gaobin Huang wrote:
> CMD_CMD_RC_TABLE ends at 001Eh (Invalid Extent List), but the command
> return code table in CXL r4.0 Table 8-208 also defines:
>
> 001Fh Transfer Out of Order: The input parameters data transfer was
> aborted because it occurred out of order.
> 0020h Request Abort Not Supported by Background Operation: The ongoing
> background operation does not support the Request Abort command.
>
> A device that reports either code is described as an unknown return code.
> Add both entries, mapped to -ENXIO.
>
> Signed-off-by: Gaobin Huang <huanggaobin23@semi.ac.cn>
> ---
> drivers/cxl/cxlmem.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/cxl/cxlmem.h b/drivers/cxl/cxlmem.h
> index c401e3a1a..43f29564c 100644
> --- a/drivers/cxl/cxlmem.h
> +++ b/drivers/cxl/cxlmem.h
> @@ -190,6 +190,8 @@ static inline struct cxl_ep *cxl_ep_load(struct cxl_port *port,
> C(FEATURETRANSFEROOO, -ENXIO, "feature transfer out of order"), \
> C(RESOURCEEXHAUSTED, -ENXIO, "resources are exhausted"), \
> C(EXTLIST, -ENXIO, "invalid Extent List"), \
> + C(TRANSFEROOO, -ENXIO, "transfer out of order"), \
> + C(REQABORTNOTSUP, -ENXIO, "request abort not supported"), \
Hi Gaobin,
Do we have users for them ? or potential users ?
Best regards,
Richard Cheng.
>
> #undef C
> #define C(a, b, c) CXL_MBOX_CMD_RC_##a
>
> base-commit: 999811aca000b0d3d1c838c60dc9db7c72eb0c73
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-10-15 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 5:50 Gaobin Huang
2026-10-15 8:16 ` Richard Cheng [this message]
2026-10-15 8:42 ` 黄高彬
2026-10-15 15:17 ` Dave Jiang
2026-10-15 17:39 ` 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=atCLjvE5xJp9jo6L@MWDK4CY14F \
--to=icheng@nvidia.com \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=djbw@kernel.org \
--cc=huanggaobin23@semi.ac.cn \
--cc=iweiny@kernel.org \
--cc=jic23@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.com \
--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
all inboxes | Powered by JetHome®