This series aims to address long-standing conflicts between dax_hmem and CXL when handling Soft Reserved memory ranges.
I have considered adding support for DAX_CXL_MODE_REGISTER, but I do not yet have a solid approach. Since this came up in discussion yesterday, I am sending the current work and would appreciate inputs on how best to handle the DAX_CXL_MODE_REGISTER case. Reworked from Dan's patch: https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git/patch/?id=ab70c6227ee6165a562c215d9dcb4a1c55620d5d Previous work: https://lore.kernel.org/all/20250715180407.47426-1-smita.koralahallichannabasa...@amd.com/ Smita Koralahalli (6): dax/hmem, e820, resource: Defer Soft Reserved registration until hmem is ready dax/hmem: Request cxl_acpi and cxl_pci before walking Soft Reserved ranges dax/hmem, cxl: Tighten dependencies on DEV_DAX_CXL and dax_hmem dax/hmem: Defer Soft Reserved overlap handling until CXL region assembly completes dax/hmem: Reintroduce Soft Reserved ranges back into the iomem tree cxl/region, dax/hmem: Guard CXL DAX region creation and tighten HMEM deps arch/x86/kernel/e820.c | 2 +- drivers/cxl/core/region.c | 4 +- drivers/dax/Kconfig | 3 + drivers/dax/hmem/device.c | 4 +- drivers/dax/hmem/hmem.c | 137 +++++++++++++++++++++++++++++++++++--- include/linux/ioport.h | 24 +++++++ kernel/resource.c | 73 +++++++++++++++++--- 7 files changed, 222 insertions(+), 25 deletions(-) -- 2.17.1
