Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 14 12月, 2009 11 次提交
    • M
      microblaze: ftrace: Add dynamic trace support · 7d241ff0
      由 Michal Simek 提交于 
      With dynamic function tracer, by default, _mcount is defined as an
"empty" function, it returns directly without any more action. When
enabling it in user-space, it will jump to a real tracing
function(ftrace_caller), and do the real job for us.

Differ from the static function tracer, dynamic function tracer provides
two functions ftrace_make_call()/ftrace_make_nop() to enable/disable the
tracing of some indicated kernel functions(set_ftrace_filter).

In the kernel version, there is only one "_mcount" string for every
kernel function, so, we just need to match this one in mcount_regex of
scripts/recordmcount.pl.

For more information please look at code and Documentation/trace folder.

Steven ACK that scripts/recordmcount.pl part.
Acked-by: NSteven Rostedt <rostedt@goodmis.org>
Signed-off-by: NMichal Simek <monstr@monstr.eu>
      7d241ff0
    • M
      microblaze: ftrace: enable HAVE_FUNCTION_TRACE_MCOUNT_TEST · 6d9e60ce
      由 Michal Simek 提交于 
      Implement MCOUNT_TEST in asm code - it is faster than use
generic code
Signed-off-by: NMichal Simek <monstr@monstr.eu>
      6d9e60ce
    • M
      microblaze: ftrace: add static function tracer · 2fd7c761
      由 Michal Simek 提交于 
      If -pg of gcc is enabled with CONFIG_FUNCTION_TRACER=y. a calling to
_mcount will be inserted into each kernel function. so, there is a
possibility to trace the kernel functions in _mcount.

This patch add the specific _mcount support for static function
tracing. by default, ftrace_trace_function is initialized as
ftrace_stub(an empty function), so, the default _mcount will introduce
very little overhead. after enabling ftrace in user-space, it will jump
to a real tracing function and do static function tracing for us.

Commit message from Wu Zhangjin <wuzhangjin@gmail.com>
Signed-off-by: NMichal Simek <monstr@monstr.eu>
      2fd7c761
    • M
      microblaze: Add TRACE_IRQFLAGS_SUPPORT · a3cd613b
      由 Michal Simek 提交于 
      There are just two major changes
Renamed local_irq functions to raw_local_irq in irq.c.
Added TRACE_IRQFLAGS_SUPPORT to Kconfig.debug.

Look at Documentation/irqflags-tracing.txt
Signed-off-by: NMichal Simek <monstr@monstr.eu>
      a3cd613b
    • M
      microblaze: preliminary enabling for LATENCYTOP support in Kconfig · fb5a32dc
      由 Michal Simek 提交于 
      Signed-off-by: NMichal Simek <monstr@monstr.eu>
      fb5a32dc
    • M
      microblaze: Lockdep support · bf2d8096
      由 Michal Simek 提交于 
      Microblaze needs to do lock_init very soon because MMU init calls lock functions.

Here is the explanation from Peter Zijlstra why we have to enable
__ARCH_WANTS_INTERRUPTS_ON_CTSW.

"So we schedule while holding rq->lock (for obvious reasons), but since
lockdep tracks held locks per tasks, we need to transfer the held state
from the prev to the next task. We do this by explicity calling
spin_release(&rq->lock) in context_switch() right before switch_to(),
and calling spin_acquire(&rq->lock) in
finish_task_switch()->finish_lock_switch().

Now, for some reason lockdep thinks that interrupts got enabled over the
context switch (git grep __ARCH_WANTS_INTERRUPTS_ON_CTSW arch/microblaze
doesn't seem to turn up anything).

Clearly trying to acquire the rq->lock with interrupts enabled is a bad
idea and lockdep warns you about this."
Signed-off-by: NMichal Simek <monstr@monstr.eu>
      bf2d8096
    • M
      microblaze: Register timecounter/cyclecounter · 519e9f41
      由 Michal Simek 提交于 
      It is the same counter as we use as free running one.
I would like to use it for ftrace.
Signed-off-by: NMichal Simek <monstr@monstr.eu>
      519e9f41
    • M
      microblaze: Stack trace support · 24b45a12
      由 Michal Simek 提交于 
      This is working implemetation but the problem is that
Microblaze misses frame pointer that's why is there
big loop which trace and show all addresses which are in text.
It shows addresses which are in registers, etc.

This is problem and this is the reason why all Microblaze
traces are wrong. There is an option to do hacks and trace
the kernel code but this is too complicated.
Signed-off-by: NMichal Simek <monstr@monstr.eu>
      24b45a12
    • M
      microblaze: Add IRQENTRY_TEXT to lds · 7cf79d59
      由 Michal Simek 提交于 
      It is important for ftrace irqsoff support
Signed-off-by: NMichal Simek <monstr@monstr.eu>
      7cf79d59
    • M
      microblaze: __init_begin symbol must be aligned · 13cdee23
      由 Michal Simek 提交于 
      The problem was that free_initmem pass to  free_initrd_mem got
bad aligned __init_begin symbol and free_initrd_mem don't care
about __init_end but take PAGE_SIZE instead.

Here is behavior in kernel bootlog.
ramdisk_execute_command from (init/main.c) was rewrite

Freeing unused kernel memory: 6224k freed
Failed to execute ��������������{���
Failed to execute ��������������{����.  Attempting defaults...
Mounting proc:
Mounting var:
Signed-off-by: NMichal Simek <monstr@monstr.eu>
      13cdee23
    • M
      microblaze: GPIO reset support · 42a2478b
      由 Michal Simek 提交于 
      Signed-off-by: NMichal Simek <monstr@monstr.eu>
      42a2478b
  3. 12 12月, 2009 29 次提交