ENUM UM_TIMETRAVEL_SCHEDSHM_CAP(9)

🕰️✨ enum um_timetravel_schedshm_cap — Kernel API Manual, bestie edition 🎀

Okay so this is enum um_timetravel_schedshm_cap(9) and it's literally the time-travel capabilities of every client — like the friend group roster of who's allowed to do what in the timestream. From the Kernel API Manual, we're vibing 💅

---

🌸 NAME 🌸

enum um_timetravel_schedshm_cap — the time travel capabilities of every client. That's it, that's the whole vibe 🦋

---

✨ SYNOPSIS ✨

enum um_timetravel_schedshm_cap {
    UM_TIMETRAVEL_SCHEDSHM_CAP_TIME_SHARE

};

Not me giving you the whole enum realness above 👑 no cap, that's exactly what it looks like.

---

💜 CONSTANTS 💜

• UM_TIMETRAVEL_SCHEDSHM_CAP_TIME_SHARE — okay so this is the main character flag 🫶. The client can read current time, update internal time request to shared memory, and read free until — and it sends no Ack on RUN and doesn't expect ACK on WAIT. Like, it's fully self-sufficient, highkey an independent queen 💅

---

🔥 DESCRIPTION 🔥

These flags have got to be set immediately after processing the ACK to the START message, and before sending any message to the controller. Timing is everything bestie, don't be out here setting flags late 😭

⭐ Lowkey important: the order here is not optional. ACK to START first, then flags, then talk to the controller. That's the sequence, periodt.

---

🦋 SEE ALSO 🦋

• Kernel file ./include/uapi/linux/um_timetravel.h
• struct um_timetravel_msg(9)
• enum um_timetravel_shared_mem_fds(9)
• enum um_timetravel_start_ack(9)
• enum um_timetravel_ops(9)
• enum um_timetravel_schedshm_flags(9)
• Time travel shared memory overview(9)
• union um_timetravel_schedshm_client(9)
• struct um_timetravel_schedshm(9)

Read them all, they're all iconic in their own way 💖

---

And that's the whole page babes 🌈 This little masterpiece lives in ./include/uapi/linux, dated October 2026, and the page footer was serving enum um_tim...schedshm_cap(9) energy. Go be the time-travel client you were always meant to be 🧚💜