Use hr_timer's active checks instead of having own flag.wip-edzl-critique

1 files changed, 8 insertions, 9 deletions

diff --git a/include/litmus/rt_param.h b/include/litmus/rt_param.h
index 53741727d5d0..63dc87b65551 100644
--- a/include/litmus/rt_param.h
+++ b/include/litmus/rt_param.h
@@ -82,14 +82,6 @@ struct rt_job {
         /* How much service has this job received so far? */
         lt_t    exec_time;
 
-#ifdef CONFIG_PLUGIN_EDZL
-        /* boolean indicating zero-laxity state.  We will
-           set this flag explicitly at zero-laxity detection.
-           This makes priority comparison operations more
-           predictable since laxity varies with time */
-        int     zero_laxity;
-#endif
-
         /* Which job is this. This is used to let user space
          * specify which job to wait for, which is important if jobs
          * overrun. If we just call sys_sleep_next_period() then we
@@ -98,6 +90,14 @@ struct rt_job {
          * Increase this sequence number when a job is released.
          */
         unsigned int    job_no;
+
+#ifdef CONFIG_PLUGIN_EDZL
+        /* boolean indicating zero-laxity state.  We will
+           set this flag explicitly at zero-laxity detection.
+           This makes priority comparison operations more
+           predictable since laxity varies with time */
+        unsigned int    zero_laxity:1;
+#endif
 };
 
 struct pfair_param;
@@ -123,7 +123,6 @@ struct rt_param {
         struct rt_job           job_params;
 
 #ifdef CONFIG_PLUGIN_EDZL
-        unsigned int            zl_timer_armed:1;
         /* used to trigger zero-laxity detection */
         struct hrtimer          zl_timer;
 #endif