Enable sched_trace log injection from userspacewip-gpu-cleanup

1 files changed, 22 insertions, 0 deletions

diff --git a/include/litmus/rt_param.h b/include/litmus/rt_param.h
index c8ee64569dbb..43daaf84101d 100644
--- a/include/litmus/rt_param.h
+++ b/include/litmus/rt_param.h
@@ -47,6 +47,28 @@ typedef enum {
         AUX_FUTURE      = (AUX_CURRENT<<2)
 } aux_flags_t;
 
+/* mirror of st_event_record_type_t
+ * Assume all are UNsupported, unless otherwise stated. */
+typedef enum {
+        ST_INJECT_NAME = 1,                             /* supported */
+        ST_INJECT_PARAM,                                /* supported */
+        ST_INJECT_RELEASE,                              /* supported */
+        ST_INJECT_ASSIGNED,
+        ST_INJECT_SWITCH_TO,
+        ST_INJECT_SWITCH_AWAY,
+        ST_INJECT_COMPLETION,                   /* supported */
+        ST_INJECT_BLOCK,
+        ST_INJECT_RESUME,
+        ST_INJECT_ACTION,
+        ST_INJECT_SYS_RELEASE,                  /* supported */
+} sched_trace_injection_events_t;
+
+struct st_inject_args {
+        lt_t release;
+        lt_t deadline;
+        unsigned int job_no;
+};
+
 /* We use the common priority interpretation "lower index == higher priority",
  * which is commonly used in fixed-priority schedulability analysis papers.
  * So, a numerically lower priority value implies higher scheduling priority,