[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Mon, 4 Apr 2011 14:58:03 -0700
From: Randy Dunlap <rdunlap@...otime.net>
To: lkml <linux-kernel@...r.kernel.org>
Cc: torvalds <torvalds@...ux-foundation.org>,
Daniel Baluta <dbaluta@...acom.com>,
Catalin Marinas <catalin.marinas@....com>
Subject: [PATCH 1/8] Documentation: update kmemleak arch. info
From: Daniel Baluta <dbaluta@...acom.com>
Besides x86 and arm, kmemleak now supports powerpc, sparc, sh,
microblaze and tile.
Signed-off-by: Daniel Baluta <dbaluta@...acom.com>
Acked-by: Catalin Marinas <catalin.marinas@....com>
Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
---
Documentation/kmemleak.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-2.6.38-git18.orig/Documentation/kmemleak.txt
+++ linux-2.6.38-git18/Documentation/kmemleak.txt
@@ -11,6 +11,7 @@ with the difference that the orphan obje
reported via /sys/kernel/debug/kmemleak. A similar method is used by the
Valgrind tool (memcheck --leak-check) to detect the memory leaks in
user-space applications.
+Kmemleak is supported on x86, arm, powerpc, sparc, sh, microblaze and tile.
Usage
-----
@@ -178,5 +179,4 @@ block doesn't need to be freed (some cas
the pointer is calculated by other methods than the usual container_of
macro or the pointer is stored in a location not scanned by kmemleak.
-Page allocations and ioremap are not tracked. Only the ARM and x86
-architectures are currently supported.
+Page allocations and ioremap are not tracked.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists