From: Alison Schofield <alison.schofield@intel.com>
To: peng guo <engguopeng@buaa.edu.cn>
Cc: dave@stgolabs.net, jonathan.cameron@huawei.com,
dave.jiang@intel.com, vishal.l.verma@intel.com,
ira.weiny@intel.com, dan.j.williams@intel.com,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
wyguopeng@163.com
Subject: Re: [PATCH v3] cxl/core: Support mbox op clear log of vendor debug logs
Date: Wed, 10 Jul 2024 11:26:56 -0700 [thread overview]
Message-ID: <Zo7ScFy2B4jFSGtb@aschofie-mobl2> (raw)
In-Reply-To: <20240710023112.8063-1-engguopeng@buaa.edu.cn>
On Wed, Jul 10, 2024 at 10:31:12AM +0800, peng guo wrote:
> When user send a mbox cmd whose opcode is CXL_MBOX_OP_CLEAR_LOG and
> the in_payload is normal vendor debug log UUID according to
> the CXL specification
> cxl_payload_from_user_allowed() will return false unexpectedly,
> Sending mobox cmd operation failed and the kernel log will print:
> Clear Log: input payload not allowed.
>
> All CXL devices that support a debug log shall support the Vendor Debug
> Log to allow the log to be accessed through a common host driver, for any
> device, all versions of the CXL specification define the same value with
> Log Identifier of: 5e1819d9-11a9-400c-811f-d60719403d86
>
> refer to:
> CXL spec r2.0 Table 169
> CXL spec r3.0 Table 8-62
> CXL spec r3.1 Table 8-71
>
> Fix the definition value of DEFINE_CXL_VENDOR_DEBUG_UUID to match the
> CXL r3.1 specification.
>
> Fixes: 472b1ce6e9d6 ("cxl/mem: Enable commands via CEL")
> Signed-off-by: peng guo <engguopeng@buaa.edu.cn>
Peng: Thanks for the patch!
DaveJ: Please fixup paragraph one split and s/mobox/mbox when applying.
Reviewed-by: Alison Schofield <alison.schofield@intel.com>
> ---
> v2 -> v3: Add a description of the impact of this issue on user usage
> Modify the fixes tag
> v1 -> v2: update commit message and addressed review comments
>
> drivers/cxl/cxlmem.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cxl/cxlmem.h b/drivers/cxl/cxlmem.h
> index af8169ccdbc0..feb1106559d2 100644
> --- a/drivers/cxl/cxlmem.h
> +++ b/drivers/cxl/cxlmem.h
> @@ -563,7 +563,7 @@ enum cxl_opcode {
> 0x3b, 0x3f, 0x17)
>
> #define DEFINE_CXL_VENDOR_DEBUG_UUID \
> - UUID_INIT(0xe1819d9, 0x11a9, 0x400c, 0x81, 0x1f, 0xd6, 0x07, 0x19, \
> + UUID_INIT(0x5e1819d9, 0x11a9, 0x400c, 0x81, 0x1f, 0xd6, 0x07, 0x19, \
> 0x40, 0x3d, 0x86)
>
> struct cxl_mbox_get_supported_logs {
> --
> 2.43.0
>
prev parent reply other threads:[~2024-07-10 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 2:31 [PATCH v3] cxl/core: Support mbox op clear log of vendor debug logs peng guo
2024-07-10 18:26 ` Alison Schofield [this message]
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=Zo7ScFy2B4jFSGtb@aschofie-mobl2 \
--to=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=engguopeng@buaa.edu.cn \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=wyguopeng@163.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.