aboutsummaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap2/sdram-qimonda-hyb18m512160af-6.h
diff options
context:
space:
mode:
authorAndrea Bastoni <bastoni@cs.unc.edu>2009-12-18 09:08:44 -0500
committerAndrea Bastoni <bastoni@cs.unc.edu>2009-12-18 09:08:44 -0500
commit2f41251f9febad2e54fa338ea63a62818970af0c (patch)
tree470e7ae6305bc554b1564579586b898fd8da5159 /arch/arm/mach-omap2/sdram-qimonda-hyb18m512160af-6.h
parent0c70a26073633b3879eac57d38f1260c1bebeafc (diff)
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 ????)
Diffstat (limited to 'arch/arm/mach-omap2/sdram-qimonda-hyb18m512160af-6.h')
0 files changed, 0 insertions, 0 deletions