telemetry_raw_read_eventlog(9)

🫶 telemetry_raw_read_eventlog — the Kernel API Manual, bestie edition

okay so we're reading telemetry_raw_read_eventlog(9) today and honestly? it's giving "small function, big responsibility" ✨ it lives in the Kernel API Manual and it's the raw, no-training-wheels version of pulling the Telemetry log out of PSS or IOSS 💅

---

✨ NAME ✨

telemetry_raw_read_eventlog — Fetch the Telemetry log from PSS or IOSS 🎀

---

✨ SYNOPSIS ✨

int telemetry_raw_read_eventlog (enum telemetry_unit telem_unit , struct
telemetry_evtlog *evtlog , int len );

like yes she's a one-liner but she's an iconic one-liner 🫶

---

🌸 ARGUMENTS 🌸

• telem_unit — Specify whether IOSS or PSS Read 👑 so you literally have to tell it which one you want, no guessing, no vibes-based defaults.
• evtlog — Array of telemetry_evtlog structs to fill data 💖 this is where the good stuff lands.
• len — Length of array of evtlog 🎀 i.e. how many structs you're handing over. pls make it correct, i'm begging 🙈

---

🦋 DESCRIPTION 🦋

The caller must take care of locking in this case. 💀

bestie this is the whole description and it's the whole point — raw means raw, so you bring the lock, not the function. no cap, if you skip that it's on you 😭

---

🌈 RETURN 🌈

• number of eventlogs read for success 🔥
• < 0 for failure 💀

like it literally tells you: count good, negative bad, iykyk ✨

---

⭐ SEE ALSO ⭐

• Kernel file ./drivers/platform/x86/intel/telemetry/core.c 📁
• telemetry_read_events(9)
• telemetry_read_eventlog(9)
• telemetry_get_trace_verbosity(9)
• telemetry_set_trace_verbosity(9)
• telemetry_set_pltdata(9)
• telemetry_clear_pltdata(9)
• telemetry_get_pltdata(9)
• telemetry_get_evtname(9)

the whole telemetry friend group, all linked up 🫶 go read the rest, they all ate 💅

---

and that's the page, bestie 🧚 this one came out of ./drivers/platform/x86/intel/t..., dated October 2026, under the Kernel API Manual banner — periodt, go lock your own mutex and slay 💜