From 1235a665a5e00dc762e6646c01381b3ed5019d86 Mon Sep 17 00:00:00 2001 From: Glenn Elliott Date: Wed, 9 Jan 2013 17:00:54 -0500 Subject: Enable sched_trace log injection from userspace --- include/litmus/rt_param.h | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) (limited to 'include/litmus/rt_param.h') 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, -- cgit v1.2.2