STRUCT CXL_MEM_COMMAND(9)

✨ struct cxl_mem_command(9) ✨

okay so this is from the Kernel API Manual bestie, and it's literally the driver's own little internal mood board for memory device commands 💅 no cap, it's giving backstage-pass energy.

🌸 NAME 🌸

struct cxl_mem_command — the driver's representation of a memory device command 🎀

🦋 SYNOPSIS 🦋

struct cxl_mem_command {
    struct cxl_command_info info;
    enum cxl_opcode opcode;
    u32 flags;
  #define CXL_CMD_FLAG_FORCE_ENABLE BIT(0);
 };

💖 Members 💖

• info — the command info exactly as it exists for the UAPI, like the official public-facing version of the vibe ✨
• opcode — the actual bits used for the mailbox protocol, i.e. the real ones doing the work 🔥
• flags — the set of flags that affect how the driver behaves 🫶

👑 Description 👑

• CXL_CMD_FLAG_FORCE_ENABLE — okay so listen: in cases of error, commands with this flag will be enabled by the driver regardless of what the hardware may have advertised. The driver said "I don't care what the hardware thinks, we're doing this" 💀 iconic honestly.

The cxl_mem_command is the driver's internal representation of the commands that are supported by the driver. And here's the tea ☕ — some of these commands may not be supported by the hardware. Not a single one of them, lowkey. The driver will use info to validate the fields the user passed in, and then it submits the opcode to the hardware. That's the whole flow, fr fr 💫

See struct cxl_command_info for the receipts 👀

🧚 SEE ALSO 🧚

Kernel file ./drivers/cxl/cxlmem.h, plus the whole friend group: struct cxl_memdev(9), struct cxl_attach_region(9), struct cxl_event_state(9), struct cxl_poison_state(9), struct cxl_fw_state(9), struct cxl_security_state(9), struct cxl_memdev_state(9), struct cxl_hdm(9) 🌈 ⭐

and that's the page bestie 🥰 brought to you by ./drivers/cxl, dated October 2026, and it's still out here being struct cxl_mem_command(9) — main character energy forever 💜🎀