pmt_telem_read32(9)

💅 pmt_telem_read32 — Kernel API Manual ✨

okay bestie, welcome to the pmt_telem_read32(9) page, straight out of the Kernel API Manual 🎀 this one's a little telemetry girly and she's literally so straightforward, you're gonna eat this up 💖

🌸 NAME 🌸

pmt_telem_read32 — read qwords from counter sram using sample id 🦋

✨ SYNOPSIS ✨

int pmt_telem_read32 (struct telem_endpoint *ep , u32 id , u32 *data ,
u32 count );

🫶 ARGUMENTS 🫶

• ep — the telemetry endpoint you're reading from, bestie 📖
• id — the beginning sample id of the metric(s) you want to read, like the starting point of the vibe check ✨
• data — an allocated dword buffer, she's where the good stuff lands 💾
• count — how many dwords you're asking for, no cap 🔢

💜 DESCRIPTION 💜

So here's the tea: callers must ensure reads are aligned ⚠️ like, that's on you, not on the function, okay?

And the big one 👀 — when the call returns -ENODEV, that means the device has been removed, and callers should unregister the telemetry endpoint. periodt. don't leave her registered, that's not the move 😭

🔥 RETURN 🔥

• 0 — Success 🎉 slay, it worked
• -ENODEV — the device is not present 🙈 she's gone
• -EINVAL — the offset is out bounds 💀 yeah that's a miss
• -EPIPE — the device was removed during the read 😱 data was written but should be considered invalid, so do not trust it, fr fr

🌈 SEE ALSO 🌈

• Kernel file ./drivers/platform/x86/intel/pmt/telemetry.h 📄
• pmt_telem_get_next_endpoint(9)
• pmt_telem_register_endpoint(9)
• pmt_telem_unregister_endpoint(9)
• pmt_telem_get_endpoint_info(9)
• pmt_telem_find_and_register_endpoint(9)
• pmt_telem_read(9)

okay that's the whole page, you understood it perfectly 💅 this lives in ./drivers/platform/x86/intel/pmt, dated October 2026, and yeah the page is literally called pmt_telem_read32(9) in case you forgot already 🧚 go read some telemetry bestie, you got this 👑