mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: 黄高彬 <huanggaobin23@semi.ac.cn>, "Richard Cheng" <icheng@nvidia.com>
Cc: linux-cxl@vger.kernel.org, Davidlohr Bueso <dave@stgolabs.net>,
	Jonathan Cameron <jic23@kernel.org>,
	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 08:17:19 -0700	[thread overview]
Message-ID: <ec305690-a036-406e-8185-d93632a5dcb7@intel.com> (raw)
In-Reply-To: <31c53d8e.42202.1a13eba4ae8.Coremail.huanggaobin23@semi.ac.cn>



On 10/15/26 1:42 AM, 黄高彬 wrote:
> Hi Richard,
> 
>> Do we have users for them ? or potential users ?
> 
> I checked the related code, and the honest answer is no for both today.
> 
> 001Fh is the code Perform Maintenance (opcode 0600h) returns when the input
> parameters are transferred in parts and the parts arrive out of order --
> Action = Initiate Transfer, Continue Transfer, End Transfer (CXL r4.0,
> 8.2.10.7).  Linux does issue Perform Maintenance: PPR and the sparing
> operations in edac.c both go through cxl_perform_maintenance().  That helper
> always transfers the parameters in a single command though -- it returns
> -ENOMEM when they do not fit in the mailbox payload instead of chunking --
> so the ordering condition cannot arise from the driver.  The multi-chunk
> flow in the specification is described for the Built-In Self-Test test
> parameters, and there is no BIST support in the driver.
> 
> 0020h is only the return code of Request Abort Background Operation (opcode
> 0005h).  Linux does not issue that command either.
> 
> So neither code has a producer in the driver today.  Both are defined in the
> command return code table (CXL r4.0 Table 8-208) that CMD_CMD_RC_TABLE
> transcribes, and carrying them costs two lines and no behavior change: a
> device that reports either already comes back as -ENXIO through the
> unknown-code path, so what the entries buy is a name instead of "unknown
> return code".
> 
> If the point is that a definition should arrive with the code that can
> produce it, that is a fair position too.  I can withdraw this patch and
> resend it together with chunked maintenance transfer support, or with abort
> support, whichever is implemented first. 

Yes lets do that.
> 
> Thanks,
> Gaobin


  reply	other threads:[~2026-10-15 15: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
2026-10-15  8:42   ` 黄高彬
2026-10-15 15:17     ` Dave Jiang [this message]
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=ec305690-a036-406e-8185-d93632a5dcb7@intel.com \
    --to=dave.jiang@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=dave@stgolabs.net \
    --cc=djbw@kernel.org \
    --cc=huanggaobin23@semi.ac.cn \
    --cc=icheng@nvidia.com \
    --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®