> But, generally, is there way to trace what happens in kernel, > something in /proc or /sys ? > Do I need to switch tracing in configuration ? I think you should look at kernel module level of Tracing. You could have tracing with something like cyclic-test. Also some tracing with options like # CONFIG_PREEMPT_RCU_TRACE is not set. > > Thanks, > Maksym. > > On 14 June 2010 11:44, Sujit K M <sjt.kar@xxxxxxxxx> wrote: >>> CONFIG_PREEMPT_RCU=y >>> # CONFIG_PREEMPT_RCU_TRACE is not set >> >> Why is RCU being set to y? >> >>> # CONFIG_PREEMPT_NONE is not set >>> # CONFIG_PREEMPT_VOLUNTARY is not set >>> # CONFIG_PREEMPT_DESKTOP is not set >> >> Fine. >> >>> CONFIG_PREEMPT_RT=y >> >> This is correct. >> >>> CONFIG_PREEMPT=y >>> CONFIG_PREEMPT_SOFTIRQS=y >>> CONFIG_PREEMPT_HARDIRQS=y >> >> I think this part is susceptible. >> >> Thanks, >> Sujit >> > -- -- Sujit K M blog(http://kmsujit.blogspot.com/) -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
