From: Catalin Marinas <catalin.marinas@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 2.6.18-rc6 06/10] Add kmemleak support for ARM
Date: Wed, 06 Sep 2006 23:37:12 +0100 [thread overview]
Message-ID: <20060906223711.21550.48239.stgit@localhost.localdomain> (raw)
In-Reply-To: <20060906223536.21550.55411.stgit@localhost.localdomain>
From: Catalin Marinas <catalin.marinas@arm.com>
This patch modifies the vmlinux.lds.S script and adds the backtrace support
for ARM to be used with kmemleak.
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
---
arch/arm/kernel/vmlinux.lds.S | 7 +++++++
include/asm-arm/processor.h | 12 ++++++++++++
2 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/arch/arm/kernel/vmlinux.lds.S b/arch/arm/kernel/vmlinux.lds.S
index 3ca574e..59976b8 100644
--- a/arch/arm/kernel/vmlinux.lds.S
+++ b/arch/arm/kernel/vmlinux.lds.S
@@ -67,6 +67,11 @@ #endif
__per_cpu_start = .;
*(.data.percpu)
__per_cpu_end = .;
+#ifdef CONFIG_DEBUG_MEMLEAK
+ __memleak_offsets_start = .;
+ *(.init.memleak_offsets)
+ __memleak_offsets_end = .;
+#endif
#ifndef CONFIG_XIP_KERNEL
__init_begin = _stext;
*(.init.data)
@@ -115,6 +120,7 @@ #endif
.data : AT(__data_loc) {
__data_start = .; /* address in memory */
+ _sdata = .;
/*
* first, the init task union, aligned
@@ -165,6 +171,7 @@ #endif
__bss_start = .; /* BSS */
*(.bss)
*(COMMON)
+ __bss_stop = .;
_end = .;
}
/* Stabs debugging sections. */
diff --git a/include/asm-arm/processor.h b/include/asm-arm/processor.h
index 04f4d34..34a3bb3 100644
--- a/include/asm-arm/processor.h
+++ b/include/asm-arm/processor.h
@@ -121,6 +121,18 @@ #define spin_lock_prefetch(x) do { } whi
#endif
+#ifdef CONFIG_FRAME_POINTER
+static inline unsigned long arch_call_address(void *frame)
+{
+ return *(unsigned long *)(frame - 4) - 4;
+}
+
+static inline void *arch_prev_frame(void *frame)
+{
+ return *(void **)(frame - 12);
+}
+#endif
+
#endif
#endif /* __ASM_ARM_PROCESSOR_H */
next prev parent reply other threads:[~2006-09-06 22:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 22:35 [PATCH 2.6.18-rc6 00/10] Kernel memory leak detector 0.10 Catalin Marinas
2006-09-06 22:36 ` [PATCH 2.6.18-rc6 01/10] Base support for kmemleak Catalin Marinas
2006-09-06 22:36 ` [PATCH 2.6.18-rc6 02/10] Some documentation " Catalin Marinas
2006-09-06 22:36 ` [PATCH 2.6.18-rc6 03/10] Add the memory allocation/freeing hooks " Catalin Marinas
2006-09-06 22:36 ` [PATCH 2.6.18-rc6 04/10] Modules support " Catalin Marinas
2006-09-06 22:37 ` [PATCH 2.6.18-rc6 05/10] Add kmemleak support for i386 Catalin Marinas
2006-09-06 22:37 ` Catalin Marinas [this message]
2006-09-06 22:37 ` [PATCH 2.6.18-rc6 07/10] Remove some of the kmemleak false positives Catalin Marinas
2006-09-06 22:37 ` [PATCH 2.6.18-rc6 08/10] Keep the __init functions after initialization Catalin Marinas
2006-09-06 22:37 ` [PATCH 2.6.18-rc6 09/10] Simple testing for kmemleak Catalin Marinas
2006-09-06 22:37 ` [PATCH 2.6.18-rc6 10/10] Update the MAINTAINERS file " Catalin Marinas
2006-09-07 0:10 ` [PATCH 2.6.18-rc6 00/10] Kernel memory leak detector 0.10 Michal Piotrowski
2006-09-07 8:04 ` Catalin Marinas
2006-09-07 8:35 ` Michal Piotrowski
2006-09-07 8:37 ` Catalin Marinas
2006-09-07 8:40 ` Michal Piotrowski
2006-09-07 8:52 ` Catalin Marinas
2006-09-07 9:05 ` Michal Piotrowski
2006-09-07 9:10 ` Catalin Marinas
2006-09-07 9:35 ` Michal Piotrowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060906223711.21550.48239.stgit@localhost.localdomain \
--to=catalin.marinas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox