devm_cxl_probe_mem(9)

🎀 devm_cxl_probe_mem(9) 🎀

okay so bestie, welcome to the Kernel API Manual entry for devm_cxl_probe_mem(9) — it’s literally giving “Add a CXL memory device and probe its region” energy, and we are gonna get you comfy with it 💖✨

🌸 NAME 🌸

devm_cxl_probe_mem — Add a CXL memory device and probe its region 🦋

✨ SYNOPSIS ✨

struct cxl_memdev * devm_cxl_probe_mem (struct cxl_dev_state *cxlds ,
       struct range *hpa_range );

🎀 ARGUMENTS 🎀

• cxlds — the CXL device state you’re associating with the memdev, bestie 🫶
• hpa_range — the CXL.mem physical address range result, iconic ✨

💅 DESCRIPTION 💅

okay so upon return, the device will have had a chance to attach to the cxl_mem driver — but plot twist 😭: it may fail to attach if the CXL topology is not ready. That means hardware CXL link down, or software platform CXL root not attached. fr fr, that’s the vibe check.

Failure to probe the memdev and/or setup a region for the memdev? Yeah, that results in this function failing. no cap, it’s a fail 💀

The parent of the resulting device and the devm context for allocations is cxlds->dev. That’s the main character for that part 👑

🌈 SEE ALSO 🌈

• Kernel file ./drivers/cxl/mem.c cxl mem(9)
• devm_cxl_add_classdev(9)

and that’s the whole devm_cxl_probe_mem(9) page, bestie 💖 source/version vibes: ./drivers/cxl; date: October 2026; manual name: devm_cxl_probe_mem(9). slay, go forth and probe responsibly ✨