xe_devcoredump_read(9)

🎀 xe_devcoredump_read(9) 🎀

🌸 NAME 🌸

okay so this page is from the Kernel API Manual, and the main character is xe_devcoredump_read(9) — she reads data from the Xe device coredump snapshot. that’s the whole name vibe, no cap. 💖

✨ SYNOPSIS ✨

here’s the signature, bestie — copy it exactly, character for character:

ssize_t xe_devcoredump_read (char *buffer , loff_t offset , size_t count
       , void *data , size_t datalen );

🦋 ARGUMENTS 🦋

• buffer — the destination buffer where the coredump data gets copied into. drop it in here.
• offset — where in the coredump data the reading starts. like a little bookmark 🔖
• count — how many bytes to read. byte budget.
• data — pointer to the xe_devcoredump structure. that’s what data points at.
• datalen — length of the data. and yes, she’s unused — the page literally says so, don’t come for me 🙈.

💅 DESCRIPTION 💅

Reads a chunk of the coredump snapshot data into the provided buffer. that’s the core move, and it ate. ✨

if the devcoredump is smaller than 1.5 GB (XE_DEVCOREDUMP_CHUNK_MAX), it is read directly from a pre-written buffer. direct read, cute and simple 🍓

for larger devcoredumps, the pre-written buffer must be periodically repopulated from the snapshot state due to kmalloc size limitations. that’s the big-coredump plot twist — no skipping that part, bestie. 😭

🔥 RETURN 🔥

Number of bytes copied on success, or a negative error code on failure. failure is giving negative error code, success is giving byte count. periodt. 💀

👑 SEE ALSO 👑

• Kernel file ./drivers/gpu/drm/xe/xe_devcoredump.c
• Xe device coredump(9)
• xe_devcoredump(9)
• xe_print_blob_ascii85(9)

mwah 💋 footer moment: source/version is ./drivers/gpu/drm/xe, date is October 2026, and the footer title is xe_devcoredump_read(9). bye bestie, go read that coredump 🫶✨