1. 29 3月, 2012 2 次提交
  2. 14 10月, 2011 2 次提交
  3. 04 8月, 2010 1 次提交
    • S
      microblaze: Add stack unwinder · ce3266c0
      Steven J. Magnani 提交于
      Implement intelligent backtracing by searching for stack frame creation,
      and emitting only return addresses. Use print_hex_dump() to display the
      entire binary kernel stack.
      
      Limitation: MMU kernels are not currently able to trace beyond a system trap
      (interrupt, syscall, etc.). It is the intent of this patch to provide
      infrastructure that can be extended to add this capability later.
      
      Changes from V1:
      * Removed checks in find_frame_creation() that prevented location of the frame
        creation instruction in heavily optimized code
      * Various formatting/commenting/file location tweaks per review comments
      * Dropped Kconfig option to enable STACKTRACE as something logically separate
      Signed-off-by: NSteven J. Magnani <steve@digidescorp.com>
      ce3266c0
  4. 16 6月, 2010 1 次提交
  5. 07 5月, 2010 2 次提交
  6. 13 4月, 2010 1 次提交
  7. 08 4月, 2010 1 次提交
  8. 07 4月, 2010 1 次提交
  9. 11 3月, 2010 1 次提交
  10. 14 12月, 2009 1 次提交
    • 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
  11. 06 7月, 2009 1 次提交
  12. 27 3月, 2009 1 次提交