Attempts to make the RHEL7 kernel work in minimal CI https://git.zx2c4.com/rhel7-kernel-misery/atom/arch/microblaze/kernel/stacktrace.c?h=master 2013-02-12T10:24:45Z 2013-02-12T10:24:45Z Michal Simek michal.simek@xilinx.com 2013-02-01T12:10:35Z urn:sha1:d64af918feb6cb81c396d6d2dabb738bc51dda3f Based on the patch: "lib: reduce the use of module.h wherever possible" (sha1: 8bc3bcc93a2b4e47d5d410146f6546bca6171663) fix all microblaze files which are not modules. Signed-off-by: Michal Simek <michal.simek@xilinx.com> 2010-08-04T08:22:35Z Steven J. Magnani steve@digidescorp.com 2010-04-27T17:37:54Z urn:sha1:ce3266c047389443d5f433d605c769e878cbe46e 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: Steven J. Magnani <steve@digidescorp.com> 2009-12-14T07:40:09Z Michal Simek monstr@monstr.eu 2009-11-10T14:57:01Z urn:sha1:24b45a12c21132e78e14f3aedf74bb1297228072 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: Michal Simek <monstr@monstr.eu>