From: "Koralahalli Channabasappa, Smita" <Smita.KoralahalliChannabasappa@amd.com>
To: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@kernel.org>,
Li Ming <ming.li@zohomail.com>,
Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
Ying Huang <huang.ying.caritas@gmail.com>,
"Xingtao Yao (Fujitsu)" <yaoxt.fnst@fujitsu.com>,
Peter Zijlstra <peterz@infradead.org>,
Greg KH <gregkh@linuxfoundation.org>,
Nathan Fontenot <nathan.fontenot@amd.com>,
Terry Bowman <terry.bowman@amd.com>,
Robert Richter <rrichter@amd.com>,
Benjamin Cheatham <benjamin.cheatham@amd.com>,
PradeepVineshReddy Kodamati <PradeepVineshReddy.Kodamati@amd.com>
Subject: Re: [PATCH v4 7/7] cxl/dax: Defer DAX consumption of SOFT RESERVED resources until after CXL region creation
Date: Wed, 9 Jul 2025 21:22:42 -0700 [thread overview]
Message-ID: <a4860c1e-e6ec-4f5a-a039-bb2066740523@amd.com> (raw)
In-Reply-To: <aac45d58-afca-487c-8d14-62d5e7fd490e@fujitsu.com>
Hi Zhijian,
Sorry for the delay in getting back on this. It took me a bit of time to
fully understand what was happening. Responses inline.
On 6/12/2025 7:12 PM, Zhijian Li (Fujitsu) wrote:
> Hi Smita, Nathan, Terry
>
> I am struggling to understand if this patch is truly necessary, or if I haven't
> fully grasped the scenario where it provides value. Without applying this patch
> on a QEMU/VM with both HMEM and CXL.mem installed, I observed no issues. (Are there
> specific config options required to reproduce the problem?)
>
> Here is the /proc/iomem without the patch:
> 180000000-1ffffffff : Soft Reserved ### 2 hmem nodes
> 180000000-1bfffffff : dax1.0
> 180000000-1bfffffff : System RAM (kmem)
> 1c0000000-1ffffffff : dax2.0
> 1c0000000-1ffffffff : System RAM (kmem)
> 5c0001128-5c00011b7 : port1
> 5d0000000-64fffffff : CXL Window 0 ### 1 CXL node
> 5d0000000-64fffffff : region0
> 5d0000000-64fffffff : dax0.0
> 5d0000000-64fffffff : System RAM (kmem)
>
> On 04/06/2025 06:19, Smita Koralahalli wrote:
>> From: Nathan Fontenot <nathan.fontenot@amd.com>
>>
>> The DAX HMEM driver currently consumes all SOFT RESERVED iomem resources
>> during initialization. This interferes with the CXL driver’s ability to
>> create regions and trim overlapping SOFT RESERVED ranges before DAX uses
>> them.
>
> When referring to "HMEM driver" in the commit message, is it
> `dax_hmem_platform_driver` or `dax_hmem_driver`? Regardless of which,
> what is the impact if one consumes all SOFT RESERVED resources?
>
> Since `hmem_register_device()` only creates HMEM devices for ranges
> *without* `IORES_DESC_CXL` which could be marked in cxl_acpi , cxl_core/cxl_dax
> should still create regions and DAX devices without conflicts.
You're correct that hmem_register_device() includes a check to skip
regions overlapping with IORES_DESC_CXL. However, this check only works
if the CXL region driver has already inserted those regions into
iomem_resource. If dax_hmem_platform_probe() runs too early (before CXL
region probing), that check fails to detect overlaps — leading to
erroneous registration.
This is what I think. I may be wrong. Also, Alison/Dan comment here:
"New approach is to not have the CXL intersecting soft reserved
resources in iomem_resource tree."..
https://lore.kernel.org/linux-cxl/ZPdoduf5IckVWQVD@aschofie-mobl2/
>
>> To resolve this, defer the DAX driver's resource consumption if the
>> cxl_acpi driver is enabled. The DAX HMEM initialization skips walking the
>> iomem resource tree in this case. After CXL region creation completes,
>> any remaining SOFT RESERVED resources are explicitly registered with the
>> DAX driver by the CXL driver.
>
> Conversely, with this patch applied, `cxl_region_softreserv_update()` attempts
> to register new HMEM devices. This may cause duplicate registrations for the
> same range (e.g., 0x180000000-0x1ffffffff), triggering warnings like:
>
> [ 14.984108] kmem dax4.0: mapping0: 0x180000000-0x1ffffffff could not reserve region
> [ 14.987204] kmem dax4.0: probe with driver kmem failed with error -16
>
> Because the HMAT initialization already registered these sub-ranges:
> 180000000-1bfffffff
> 1c0000000-1ffffffff
>
>
> If I'm missing something, please correct me.
Yeah, this bug is due to a double invocation of hmem_register_device()
once from cxl_softreserv_mem_register() and once from
dax_hmem_platform_probe().
When CONFIG_CXL_ACPI=y, walk_iomem_res_desc() is skipped in hmem_init(),
so I expected hmem_active to remain empty. However, I missed the detail
that the ACPI HMAT parser (drivers/acpi/numa/hmat.c) calls
hmem_register_resource(), which populates hmem_active via
__hmem_register_resource().
Case 1 (No bug): If dax_hmem_platform_probe() runs when hmem_active is
still empty.
walk_hmem_resources() walks nothing — it's effectively a no-op.
Later, cxl_softreserv_mem_register() is invoked to register leftover
soft-reserved regions via hmem_register_device().
Only one registration occurs, no conflict.
Case 2: If dax_hmem_platform_probe() runs after hmem_active is populated
by hmat_register_target_devices() (via hmem_register_resource()):
walk_hmem_resources() iterates those regions. It invokes
hmem_register_device(). Later, cxl_region driver does the same again.
This results in duplicate instances for the same physical range and
second call fails like below:
[ 14.984108] kmem dax4.0: mapping0: 0x180000000-0x1ffffffff could not
reserve region
[ 14.987204] kmem dax4.0: probe with driver kmem failed with error -16
Below, did the job to fix the above bug for me and I did incorporate
this in v5.
static int dax_hmem_platform_probe(struct platform_device *pdev)
{
+ if (IS_ENABLED(CONFIG_CXL_ACPI))
+ return 0;
dax_hmem_pdev = pdev;
return walk_hmem_resources(hmem_register_device);
}
Let me know if my thought process is right. I would appreciate any
additional feedback or suggestions.
Meanwhile, I should also mention that my approach fails, if cxl_acpi
finishes probing before dax_hmem is even loaded, it attempts to call
into unresolved dax_hmem symbols, causing probe failures. Particularly
when CXL_BUS=y and DEV_DAX_HMEM=m.
ld: vmlinux.o: in function `cxl_softreserv_mem_register':
region.c:(.text+0xc15160): undefined reference to `hmem_register_device'
make[2]: *** [scripts/Makefile.vmlinux:77: vmlinux] Error 1
I spent some time exploring possible fixes for this symbol dependency
issue, which delayed my v5 submission. I would welcome any ideas..
In the meantime, I noticed your new patchset that introduces a different
approach for resolving resource conflicts between CMFW and Soft Reserved
regions. I will take a closer look at that.
Thanks
Smita
>
> Thanks,
> Zhijian
>
>
>
>>
>> This sequencing ensures proper handling of overlaps and fixes hotplug
>> failures.
>>
>> Co-developed-by: Nathan Fontenot <Nathan.Fontenot@amd.com>
>> Signed-off-by: Nathan Fontenot <Nathan.Fontenot@amd.com>
>> Co-developed-by: Terry Bowman <terry.bowman@amd.com>
>> Signed-off-by: Terry Bowman <terry.bowman@amd.com>
>> Signed-off-by: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>
>> ---
>> drivers/cxl/core/region.c | 10 +++++++++
>> drivers/dax/hmem/device.c | 43 ++++++++++++++++++++-------------------
>> drivers/dax/hmem/hmem.c | 3 ++-
>> include/linux/dax.h | 6 ++++++
>> 4 files changed, 40 insertions(+), 22 deletions(-)
>>
>> diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
>> index 3a5ca44d65f3..c6c0c7ba3b20 100644
>> --- a/drivers/cxl/core/region.c
>> +++ b/drivers/cxl/core/region.c
>> @@ -10,6 +10,7 @@
>> #include <linux/sort.h>
>> #include <linux/idr.h>
>> #include <linux/memory-tiers.h>
>> +#include <linux/dax.h>
>> #include <cxlmem.h>
>> #include <cxl.h>
>> #include "core.h"
>> @@ -3553,6 +3554,11 @@ static struct resource *normalize_resource(struct resource *res)
>> return NULL;
>> }
>>
>> +static int cxl_softreserv_mem_register(struct resource *res, void *unused)
>> +{
>> + return hmem_register_device(phys_to_target_node(res->start), res);
>> +}
>> +
>> static int __cxl_region_softreserv_update(struct resource *soft,
>> void *_cxlr)
>> {
>> @@ -3590,6 +3596,10 @@ int cxl_region_softreserv_update(void)
>> __cxl_region_softreserv_update);
>> }
>>
>> + /* Now register any remaining SOFT RESERVES with DAX */
>> + walk_iomem_res_desc(IORES_DESC_SOFT_RESERVED, IORESOURCE_MEM,
>> + 0, -1, NULL, cxl_softreserv_mem_register);
>> +
>> return 0;
>> }
>> EXPORT_SYMBOL_NS_GPL(cxl_region_softreserv_update, "CXL");
>> diff --git a/drivers/dax/hmem/device.c b/drivers/dax/hmem/device.c
>> index 59ad44761191..cc1ed7bbdb1a 100644
>> --- a/drivers/dax/hmem/device.c
>> +++ b/drivers/dax/hmem/device.c
>> @@ -8,7 +8,6 @@
>> static bool nohmem;
>> module_param_named(disable, nohmem, bool, 0444);
>>
>> -static bool platform_initialized;
>> static DEFINE_MUTEX(hmem_resource_lock);
>> static struct resource hmem_active = {
>> .name = "HMEM devices",
>> @@ -35,9 +34,7 @@ EXPORT_SYMBOL_GPL(walk_hmem_resources);
>>
>> static void __hmem_register_resource(int target_nid, struct resource *res)
>> {
>> - struct platform_device *pdev;
>> struct resource *new;
>> - int rc;
>>
>> new = __request_region(&hmem_active, res->start, resource_size(res), "",
>> 0);
>> @@ -47,21 +44,6 @@ static void __hmem_register_resource(int target_nid, struct resource *res)
>> }
>>
>> new->desc = target_nid;
>> -
>> - if (platform_initialized)
>> - return;
>> -
>> - pdev = platform_device_alloc("hmem_platform", 0);
>> - if (!pdev) {
>> - pr_err_once("failed to register device-dax hmem_platform device\n");
>> - return;
>> - }
>> -
>> - rc = platform_device_add(pdev);
>> - if (rc)
>> - platform_device_put(pdev);
>> - else
>> - platform_initialized = true;
>> }
>>
>> void hmem_register_resource(int target_nid, struct resource *res)
>> @@ -83,9 +65,28 @@ static __init int hmem_register_one(struct resource *res, void *data)
>>
>> static __init int hmem_init(void)
>> {
>> - walk_iomem_res_desc(IORES_DESC_SOFT_RESERVED,
>> - IORESOURCE_MEM, 0, -1, NULL, hmem_register_one);
>> - return 0;
>> + struct platform_device *pdev;
>> + int rc;
>> +
>> + if (!IS_ENABLED(CONFIG_CXL_ACPI)) {
>> + walk_iomem_res_desc(IORES_DESC_SOFT_RESERVED,
>> + IORESOURCE_MEM, 0, -1, NULL,
>> + hmem_register_one);
>> + }
>> +
>> + pdev = platform_device_alloc("hmem_platform", 0);
>> + if (!pdev) {
>> + pr_err("failed to register device-dax hmem_platform device\n");
>> + return -1;
>> + }
>> +
>> + rc = platform_device_add(pdev);
>> + if (rc) {
>> + pr_err("failed to add device-dax hmem_platform device\n");
>> + platform_device_put(pdev);
>> + }
>> +
>> + return rc;
>> }
>>
>> /*
>> diff --git a/drivers/dax/hmem/hmem.c b/drivers/dax/hmem/hmem.c
>> index 3aedef5f1be1..a206b9b383e4 100644
>> --- a/drivers/dax/hmem/hmem.c
>> +++ b/drivers/dax/hmem/hmem.c
>> @@ -61,7 +61,7 @@ static void release_hmem(void *pdev)
>> platform_device_unregister(pdev);
>> }
>>
>> -static int hmem_register_device(int target_nid, const struct resource *res)
>> +int hmem_register_device(int target_nid, const struct resource *res)
>> {
>> struct device *host = &dax_hmem_pdev->dev;
>> struct platform_device *pdev;
>> @@ -124,6 +124,7 @@ static int hmem_register_device(int target_nid, const struct resource *res)
>> platform_device_put(pdev);
>> return rc;
>> }
>> +EXPORT_SYMBOL_GPL(hmem_register_device);
>>
>> static int dax_hmem_platform_probe(struct platform_device *pdev)
>> {
>> diff --git a/include/linux/dax.h b/include/linux/dax.h
>> index a4ad3708ea35..5052dca8b3bc 100644
>> --- a/include/linux/dax.h
>> +++ b/include/linux/dax.h
>> @@ -299,10 +299,16 @@ static inline int dax_mem2blk_err(int err)
>>
>> #ifdef CONFIG_DEV_DAX_HMEM_DEVICES
>> void hmem_register_resource(int target_nid, struct resource *r);
>> +int hmem_register_device(int target_nid, const struct resource *res);
>> #else
>> static inline void hmem_register_resource(int target_nid, struct resource *r)
>> {
>> }
>> +
>> +static inline int hmem_register_device(int target_nid, const struct resource *res)
>> +{
>> + return 0;
>> +}
>> #endif
>>
>> typedef int (*walk_hmem_fn)(int target_nid, const struct resource *res);
next prev parent reply other threads:[~2025-07-10 4:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 22:19 [PATCH v4 0/7] Add managed SOFT RESERVE resource handling Smita Koralahalli
2025-06-03 22:19 ` [PATCH v4 1/7] cxl/region: Avoid null pointer dereference in is_cxl_region() Smita Koralahalli
2025-06-03 23:49 ` Dave Jiang
2025-06-04 19:56 ` Nathan Fontenot
2025-06-25 15:23 ` Robert Richter
2025-06-03 22:19 ` [PATCH v4 2/7] cxl/core: Remove CONFIG_CXL_SUSPEND and always build suspend.o Smita Koralahalli
2025-06-09 11:02 ` Jonathan Cameron
2025-06-09 23:25 ` Koralahalli Channabasappa, Smita
2025-06-10 9:38 ` Jonathan Cameron
2025-06-03 22:19 ` [PATCH v4 3/7] cxl/pci: Add pci_loaded tracking to mark PCI driver readiness Smita Koralahalli
2025-06-04 9:29 ` Zhijian Li (Fujitsu)
2025-06-03 22:19 ` [PATCH v4 4/7] cxl/acpi: Add background worker to wait for cxl_pci and cxl_mem probe Smita Koralahalli
2025-06-03 23:45 ` Dave Jiang
2025-06-04 18:31 ` Koralahalli Channabasappa, Smita
2025-06-04 9:40 ` Zhijian Li (Fujitsu)
2025-06-04 14:35 ` Dave Jiang
2025-06-05 2:18 ` Zhijian Li (Fujitsu)
2025-06-03 22:19 ` [PATCH v4 5/7] cxl/region: Introduce SOFT RESERVED resource removal on region teardown Smita Koralahalli
2025-06-06 4:16 ` Zhijian Li (Fujitsu)
2025-06-06 17:53 ` Koralahalli Channabasappa, Smita
2025-06-09 12:54 ` Jonathan Cameron
2025-06-10 1:25 ` Koralahalli Channabasappa, Smita
2025-06-10 9:37 ` Jonathan Cameron
2025-06-25 15:20 ` Robert Richter
2025-07-09 1:14 ` Alison Schofield
2025-06-03 22:19 ` [PATCH v4 6/7] dax/hmem: Save the DAX HMEM platform device pointer Smita Koralahalli
2025-06-05 16:54 ` Dave Jiang
2025-06-06 8:11 ` Zhijian Li (Fujitsu)
2025-06-06 20:09 ` Nathan Fontenot
2025-06-03 22:19 ` [PATCH v4 7/7] cxl/dax: Defer DAX consumption of SOFT RESERVED resources until after CXL region creation Smita Koralahalli
2025-06-09 13:01 ` Jonathan Cameron
2025-06-13 2:12 ` Zhijian Li (Fujitsu)
2025-07-10 4:22 ` Koralahalli Channabasappa, Smita [this message]
2025-07-10 8:18 ` Zhijian Li (Fujitsu)
2025-07-15 16:27 ` Alison Schofield
2025-07-15 18:19 ` Koralahalli Channabasappa, Smita
2025-07-15 18:45 ` Alison Schofield
2025-06-04 8:43 ` [PATCH v4 0/7] Add managed SOFT RESERVE resource handling Zhijian Li (Fujitsu)
2025-06-04 18:59 ` Koralahalli Channabasappa, Smita
2025-06-16 1:00 ` Zhijian Li (Fujitsu)
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=a4860c1e-e6ec-4f5a-a039-bb2066740523@amd.com \
--to=smita.koralahallichannabasappa@amd.com \
--cc=PradeepVineshReddy.Kodamati@amd.com \
--cc=alison.schofield@intel.com \
--cc=benjamin.cheatham@amd.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=gregkh@linuxfoundation.org \
--cc=huang.ying.caritas@gmail.com \
--cc=ira.weiny@intel.com \
--cc=jack@suse.cz \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jonathan.cameron@huawei.com \
--cc=len.brown@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=ming.li@zohomail.com \
--cc=nathan.fontenot@amd.com \
--cc=nvdimm@lists.linux.dev \
--cc=pavel@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rrichter@amd.com \
--cc=terry.bowman@amd.com \
--cc=vishal.l.verma@intel.com \
--cc=willy@infradead.org \
--cc=yaoxt.fnst@fujitsu.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®