wakeup tracer not able to capture traces on 3.4 kernel

Hi, I trying to capture traces through wakeup tracer, but not able to capture it on 3.4 kernel with cortex A9 processor, armv7. {{{ / # mount -t debugfs nodev /debug / # sysctl kernel.ftrace_enabled=1 kernel.ftrace_enabled = 1 / # echo wakeup > /debug/tracing/current_tracer / # echo latency-format

Re: wakeup tracer not able to capture traces on 3.4 kernel

On Thu, Aug 29, 2013 at 7:41 PM, Prabhat Kumar Ravi wrote: > Hi, > > I trying to capture traces through wakeup tracer, but not able to > capture it on 3.4 kernel with cortex A9 processor, armv7. > {{{ > / # mount -t debugfs nodev /debug > / # sysctl kernel.ftrace_enabled=1 &g

Re: wakeup tracer not able to capture traces on 3.4 kernel

Thanks to all, I got solution, this issue is due to lack of proper timer implementation. On Thu, Aug 29, 2013 at 8:42 PM, Prabhat Kumar Ravi wrote: > On Thu, Aug 29, 2013 at 7:41 PM, Prabhat Kumar Ravi > wrote: >> Hi, >> >> I trying to capture traces through wakeup

vmlinux symtab matching kallsyms fails: dso__find_symbol_by_name ---- end ----

Hi All, On 3.4-rc49, I got following failure running `perf test`: / # perf test -v 1 1: vmlinux symtab matches kallsyms: --- start --- dso__find_symbol_by_name end vmlinux symtab matches kallsyms: FAILED! Perf test is failing at dsofind_symbol_by_name where kallsyms_map = ma

Re: 3.10-rc6 "perf test" seems unhappy

Hi, On Wed, Jun 26, 2013 at 4:39 PM, Andy Green wrote: > Hi - > > Running perf test on 3.10-rc6 gives some unexpected behaviours. > > This is on a dual Cortex A9 board with perf userland cross-built from > same tree as the kernel. > > root@aa9-eb:~# perf test > 1: vmlinux symtab matches kallsyms

x86 like DEBUG_PAGEALLOC for ARM

Hi all, As in our present ARM kernel we don't have feature like DEBUG_PAGEALLOC which generate exception if a program touched the unmaped pages. Trying to implement kernel_map_pages() for ARM, Can anyone help me in that. Regards, Prabhat -- To unsubscribe from this list: send the line "unsubsc