From: Li Ming <ming.li@zohomail.com>
To: Alison Schofield <alison.schofield@intel.com>
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,
shiju.jose@huawei.com, andriy.shevchenko@linux.intel.com,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] cxl/edac: Fix wrong dpa checking for PPR operation
Date: Wed, 9 Jul 2025 15:13:09 +0800 [thread overview]
Message-ID: <86bcfb22-f9e7-4b2a-a51b-d8d63d423fcc@zohomail.com> (raw)
In-Reply-To: <aG3I9ooPm0eJnMPn@aschofie-mobl2.lan>
On 7/9/2025 9:42 AM, Alison Schofield wrote:
> On Tue, Jul 08, 2025 at 01:15:35PM +0800, Li Ming wrote:
>> DPA 0 is considered invalid in cxl_do_ppr(), but per Table 8-143. "Get
>> Partition Info Output Payload" in CXL r3.2 section 8.2.10.9.2.1 "Get
>> Partition Info(Opcode 4100h)", it mentions that DPA 0 is a valid address
>> of a CXL device. So the correct implementation should be checking if the
>> DPA is in the DPA range of the CXL device rather than checking if the
>> DPA is equal to 0.
>>
> If it needs a fixes tag, doesn't it also need a user visible impact
> statement? I get that the PPR won't happen. What does that look like
> to the user? Is there a user level error message we can add to the
> commit log?
>
> With that, you can add:
> Reviewed-by: Alison Schofield <alison.schofield@intel.com>
>
Will do. Thanks.
Ming
>
>> Fixes: be9b359e056a ("cxl/edac: Add CXL memory device soft PPR control feature")
>> Signed-off-by: Li Ming <ming.li@zohomail.com>
>> Tested-by: Shiju Jose <shiju.jose@huawei.com>
>> Reviewed-by: Shiju Jose <shiju.jose@huawei.com>
>> ---
>> drivers/cxl/core/edac.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/cxl/core/edac.c b/drivers/cxl/core/edac.c
>> index 623aaa4439c4..1cf65b1538b9 100644
>> --- a/drivers/cxl/core/edac.c
>> +++ b/drivers/cxl/core/edac.c
>> @@ -1923,8 +1923,11 @@ static int cxl_ppr_set_nibble_mask(struct device *dev, void *drv_data,
>> static int cxl_do_ppr(struct device *dev, void *drv_data, u32 val)
>> {
>> struct cxl_ppr_context *cxl_ppr_ctx = drv_data;
>> + struct cxl_memdev *cxlmd = cxl_ppr_ctx->cxlmd;
>> + struct cxl_dev_state *cxlds = cxlmd->cxlds;
>>
>> - if (!cxl_ppr_ctx->dpa || val != EDAC_DO_MEM_REPAIR)
>> + if (!resource_contains_addr(&cxlds->dpa_res, cxl_ppr_ctx->dpa) ||
>> + val != EDAC_DO_MEM_REPAIR)
>> return -EINVAL;
>>
>> return cxl_mem_perform_ppr(cxl_ppr_ctx);
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2025-07-09 7:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 5:15 [PATCH v3 0/3] Fix wrong dpa checking in " Li Ming
2025-07-08 5:15 ` [PATCH v3 1/3] cxl/core: Introduce a new helper resource_contains_addr() Li Ming
2025-07-08 13:20 ` Andy Shevchenko
2025-07-09 3:45 ` Li Ming
2025-07-09 1:24 ` Alison Schofield
2025-07-08 5:15 ` [PATCH v3 2/3] cxl/edac: Fix wrong dpa checking for PPR operation Li Ming
2025-07-08 23:11 ` Dave Jiang
2025-07-09 1:42 ` Alison Schofield
2025-07-09 7:13 ` Li Ming [this message]
2025-07-08 5:15 ` [PATCH v3 3/3] cxl/core: Using resource_contains_addr() to check address availability Li Ming
2025-07-08 23:11 ` Dave Jiang
2025-07-09 1:37 ` 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=86bcfb22-f9e7-4b2a-a51b-d8d63d423fcc@zohomail.com \
--to=ming.li@zohomail.com \
--cc=alison.schofield@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shiju.jose@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
all inboxes | Powered by JetHome®