cxl_mem_get_event_records(9)

✨ cxl_mem_get_event_records(9) ✨

okay so bestie, this one is from the Kernel API Manual, and it is literally about grabbing event records off the device. 🎀

💅 NAME 💅

cxl_mem_get_event_records — Get Event Records from the device 🦋

🌸 SYNOPSIS 🌸

void cxl_mem_get_event_records (struct cxl_memdev_state *mds , u32
       status );

🫶 ARGUMENTS 🫶

• mds — struct cxl_memdev_state *: the driver data for the operation. This is the main-character context bestie. 💖
• status — u32: the Event Status register value identifying which events are available. It’s giving “which ones are actually on the menu” energy. ✨

🔥 DESCRIPTION 🔥

Retrieve all event records available on the device, report them as trace events, and clear them. No cap, it grabs the whole little event stack, tells you about it via trace events, and then wipes them. 🧹💫

See CXL rev 3.0 8.2.9.2.2 Get Event Records and CXL rev 3.0 8.2.9.2.3 Clear Event Records for the spec tea. 📚☕

🦋 SEE ALSO 🦋

Kernel file ./drivers/cxl/core/mbox.c and cxl mbox(9), plus the whole friend group:

• 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_partition_info(9)
• cxl_dev_state_identify(9)
• cxl_mem_sanitize(9)

mwah 💖 this page lives under ./drivers/cxl/core, and it’s dated October 2026. periodt. 👑🌈