Test kernel tracing events capabilitiestracing-devel

Can events be applied to LITMUS code instead of sched_task_trace ?

PROS:
	- architectural indipendency
	- easy porting on newer kernel version
	- lock free ring buffer implementation already there

CONS:
	- need userspace tools conversion to slightly different format
	- is it possible to replicate all the previous functionalities?
	- only sched_trace_* functions can be implemented through events,
	  TRACE() debugging features are still implemented in the old way
	  (??? cannot we simply use the tracing features of the kernel for
	   debugging purposes ????)

1 files changed, 2 insertions, 1 deletions

diff --git a/kernel/sched.c b/kernel/sched.c
index ee894ee8a0bb..5ff48213781c 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -5459,7 +5459,8 @@ need_resched:
         release_kernel_lock(prev);
 need_resched_nonpreemptible:
         TS_SCHED_START;
-        sched_trace_task_switch_away(prev);
+//      sched_trace_task_switch_away(prev);
+        trace_litmus_switch_away(prev);
 
         schedule_debug(prev);