cxl_mem_get_partition_info(9)

💅 cxl_mem_get_partition_info(9) — from the Kernel API Manual, bestie

okay so picture this: you're deep in the CXL driver, the kernel API manual is open, and you just need the tea on this device's partitions. this page (yes, the cxl_mem_get_partition_info(9) one, straight out of the Kernel API Manual) is gonna tell you everything. let's go 🎀

---

✨ NAME ✨

cxl_mem_get_partition_info — Get partition info. that's it, that's the whole vibe. 🌸

---

✨ SYNOPSIS ✨

int cxl_mem_get_partition_info (struct cxl_memdev_state *mds );

---

✨ ARGUMENTS ✨

• mds — the driver data for the operation. she's the main character here, everything runs through her 💅

---

✨ DESCRIPTION ✨

so the whole point: this retrieves the current partition info for the device you specified. 🔥

the active values are the current capacity in bytes. literally just what's allocated right now.

and then — and this is the part you gotta pay attention to, bestie — if the 'next' values are not 0, those are the pending values, in bytes, that don't hit until the next cold reset. 😭 so like. don't panic when the numbers don't match yet. they're on the way, they just need a cold reset to actually take affect.

see CXL 8.2.9.5.2.1 Get Partition Info for the full lore 📖✨

---

✨ RETURN ✨

0 if no error ✨ — or the result of the mailbox command. either way, you get a number back, it's giving very straightforward 🫶

---

✨ SEE ALSO ✨

the whole friend group, no cap:

• Kernel file ./drivers/cxl/core/mbox.c
• cxl mbox(9)
• cxl_internal_send_cmd(9)
• cxl_payload_from_user_allowed(9)
• cxl_validate_cmd_from_user(9)
• handle_mailbox_cmd_from_user(9)
• cxl_walk_cel(9)
• cxl_enumerate_cmds(9)
• cxl_mem_get_event_records(9)
• cxl_dev_state_identify(9)
• cxl_mem_sanitize(9)

like i said. iconic lineup. iykyk 👑

---

okay that's the whole page!! 💜 this one lives at ./drivers/cxl/core, dated October 2026, and yeah — it's cxl_mem_get_partition_info(9) through and through. go forth and read your partition info, bestie 🦋⭐