ENUM UM_TIMETRAVEL_SCHEDSHM_FLAGS(9)

💖 NAME 💖

Okay so this is the Kernel API Manual page for enum um_timetravel_schedshm_flags(9), and it's literally the time travel flags of every client, bestie. That's the whole vibe check. 💅✨

✨ SYNOPSIS ✨

enum um_timetravel_schedshm_flags {
    UM_TIMETRAVEL_SCHEDSHM_FLAGS_REQ_RUN

};

🎀 Constants 🎀

• UM_TIMETRAVEL_SCHEDSHM_FLAGS_REQ_RUN — the client has a request to run. It's set by client when it has a request to run, if (and only if) the running_id points to a client that is able to use shared memory, i.e. has UM_TIMETRAVEL_SCHEDSHM_CAP_TIME_SHARE (this includes the client itself). Otherwise, a message must be used. No cap, those conditions are the whole rule. 🔥

🌈 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_cap(9)
• Time travel shared memory overview(9)
• union um_timetravel_schedshm_client(9)
• struct um_timetravel_schedshm(9)

Okay that's the whole page, bestie — mwah 💋. This one comes from ./include/uapi/linux, dated October 2026, and it's the enum um_timetravel_schedshm_flags(9) manual page. Go slay your time-travel scheduling! 🫶✨