From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: <shiju.jose@huawei.com>
Cc: <dave.jiang@intel.com>, <dan.j.williams@intel.com>,
<alison.schofield@intel.com>, <vishal.l.verma@intel.com>,
<ira.weiny@intel.com>, <dave@stgolabs.net>,
<linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>, <tanxiaofei@huawei.com>,
<prime.zeng@hisilicon.com>
Subject: Re: [PATCH v3 6/6] cxl/test: Update test code for event records to CXL spec rev 3.1
Date: Fri, 25 Oct 2024 13:50:56 +0100 [thread overview]
Message-ID: <20241025135056.00003932@Huawei.com> (raw)
In-Reply-To: <20241025114555.1363-7-shiju.jose@huawei.com>
On Fri, 25 Oct 2024 12:45:55 +0100
<shiju.jose@huawei.com> wrote:
> From: Shiju Jose <shiju.jose@huawei.com>
>
> Update test code for General Media, DRAM, Memory Module Event
> Records to CXL spec rev 3.1.
>
> Signed-off-by: Shiju Jose <shiju.jose@huawei.com>
I ran the test and it looked sensible.
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Tested-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Side note, cxl_test fails on ARM due to attempting to hotplug
memory outside of the PA range the system supports. Problem
for another day when I'll either fix it post a proper bug report.
Jonathan
> ---
> tools/testing/cxl/test/mem.c | 23 ++++++++++++++++++++---
> 1 file changed, 20 insertions(+), 3 deletions(-)
>
> diff --git a/tools/testing/cxl/test/mem.c b/tools/testing/cxl/test/mem.c
> index ad5c4c18c5c6..614783eb3f84 100644
> --- a/tools/testing/cxl/test/mem.c
> +++ b/tools/testing/cxl/test/mem.c
> @@ -401,6 +401,10 @@ struct cxl_test_gen_media gen_media = {
> .channel = 1,
> .rank = 30,
> },
> + .component_id = { 0x3, 0x74, 0xc5, 0x8, 0x9a, 0x1a, 0xb, 0xfc, 0xd2, 0x7e, 0x2f, 0x31, 0x9b, 0x3c, 0x81, 0x4d },
> + .cme_threshold_ev_flags = 3,
> + .cme_count = { 33, 0, 0 },
> + .sub_type = 0x2,
> },
> };
>
> @@ -429,6 +433,11 @@ struct cxl_test_dram dram = {
> .bank_group = 5,
> .bank = 2,
> .column = {0xDE, 0xAD},
> + .component_id = { 0x1, 0x74, 0xc5, 0x8, 0x9a, 0x1a, 0xb, 0xfc, 0xd2, 0x7e, 0x2f, 0x31, 0x9b, 0x3c, 0x81, 0x4d },
> + .sub_channel = 8,
> + .cme_threshold_ev_flags = 2,
> + .cvme_count = { 14, 0, 0 },
> + .sub_type = 0x5,
> },
> };
>
> @@ -456,7 +465,10 @@ struct cxl_test_mem_module mem_module = {
> .dirty_shutdown_cnt = { 0xde, 0xad, 0xbe, 0xef },
> .cor_vol_err_cnt = { 0xde, 0xad, 0xbe, 0xef },
> .cor_per_err_cnt = { 0xde, 0xad, 0xbe, 0xef },
> - }
> + },
> + /* .validity_flags = <set below> */
> + .component_id = { 0x2, 0x74, 0xc5, 0x8, 0x9a, 0x1a, 0xb, 0xfc, 0xd2, 0x7e, 0x2f, 0x31, 0x9b, 0x3c, 0x81, 0x4d },
> + .event_sub_type = 0x3,
> },
> };
>
> @@ -478,13 +490,18 @@ static int mock_set_timestamp(struct cxl_dev_state *cxlds,
>
> static void cxl_mock_add_event_logs(struct mock_event_store *mes)
> {
> - put_unaligned_le16(CXL_GMER_VALID_CHANNEL | CXL_GMER_VALID_RANK,
> + put_unaligned_le16(CXL_GMER_VALID_CHANNEL | CXL_GMER_VALID_RANK |
> + CXL_GMER_VALID_COMPONENT | CXL_GMER_VALID_COMPONENT_ID_FORMAT,
> &gen_media.rec.media_hdr.validity_flags);
>
> put_unaligned_le16(CXL_DER_VALID_CHANNEL | CXL_DER_VALID_BANK_GROUP |
> - CXL_DER_VALID_BANK | CXL_DER_VALID_COLUMN,
> + CXL_DER_VALID_BANK | CXL_DER_VALID_COLUMN | CXL_DER_VALID_SUB_CHANNEL |
> + CXL_DER_VALID_COMPONENT | CXL_DER_VALID_COMPONENT_ID_FORMAT,
> &dram.rec.media_hdr.validity_flags);
>
> + put_unaligned_le16(CXL_MMER_VALID_COMPONENT | CXL_MMER_VALID_COMPONENT_ID_FORMAT,
> + &mem_module.rec.validity_flags);
> +
> mes_add_event(mes, CXL_EVENT_TYPE_INFO, &maint_needed);
> mes_add_event(mes, CXL_EVENT_TYPE_INFO,
> (struct cxl_event_record_raw *)&gen_media);
prev parent reply other threads:[~2024-10-25 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 11:45 [PATCH v3 0/6] Update Event Records to CXL spec rev 3.1 shiju.jose
2024-10-25 11:45 ` [PATCH v3 1/6] cxl/events: Update Common Event Record " shiju.jose
2024-10-25 11:45 ` [PATCH v3 2/6] cxl/events: Add Component Identifier formatting for " shiju.jose
2024-10-25 12:49 ` Jonathan Cameron
2024-10-25 11:45 ` [PATCH v3 3/6] cxl/events: Update General Media Event Record to " shiju.jose
2024-10-25 11:45 ` [PATCH v3 4/6] cxl/events: Update DRAM " shiju.jose
2024-10-25 11:45 ` [PATCH v3 5/6] cxl/events: Update Memory Module " shiju.jose
2024-10-25 11:45 ` [PATCH v3 6/6] cxl/test: Update test code for event records " shiju.jose
2024-10-25 12:50 ` Jonathan Cameron [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=20241025135056.00003932@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@hisilicon.com \
--cc=shiju.jose@huawei.com \
--cc=tanxiaofei@huawei.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