From: Randy Dunlap <rdunlap@xenotime.net>
To: lkml <linux-kernel@vger.kernel.org>
Cc: torvalds <torvalds@linux-foundation.org>,
Daniel Baluta <dbaluta@ixiacom.com>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: [PATCH 1/8] Documentation: update kmemleak arch. info
Date: Mon, 4 Apr 2011 14:58:03 -0700 [thread overview]
Message-ID: <20110404145803.8663081d.rdunlap@xenotime.net> (raw)
From: Daniel Baluta <dbaluta@ixiacom.com>
Besides x86 and arm, kmemleak now supports powerpc, sparc, sh,
microblaze and tile.
Signed-off-by: Daniel Baluta <dbaluta@ixiacom.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.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.
next reply other threads:[~2011-04-04 22:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 21:58 Randy Dunlap [this message]
2011-04-04 21:59 ` [PATCH 2/8] kernel/signal.c: fix typos and coding style Randy Dunlap
2011-04-04 22:00 ` [PATCH 3/8] kernel/signal.c: add kernel-doc notation to syscalls Randy Dunlap
2011-04-05 8:32 ` Matt Fleming
2011-04-08 17:41 ` Randy Dunlap
2011-04-08 17:53 ` [PATCH] signal.c: fix erroneous syscall kernel-doc Randy Dunlap
2011-04-08 20:13 ` Matt Fleming
2011-04-04 22:02 ` [PATCH 4/8] Documentation: update panic parameter info Randy Dunlap
2011-04-04 22:04 ` [PATCH 5/8] Documentation: fix minor typos/spelling Randy Dunlap
2011-04-04 22:06 ` [PATCH 6/8] kemleak-test: build as module only Randy Dunlap
2011-04-04 22:08 ` [PATCH 7/8] Documentation: consolidate leds files to leds/ subdir Randy Dunlap
2011-04-05 0:54 ` Linus Torvalds
2011-04-05 8:25 ` Antonio Ospite
2011-04-04 22:10 ` [PATCH 8/8] Documentation: update cgroups info user groups names Randy Dunlap
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=20110404145803.8663081d.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=catalin.marinas@arm.com \
--cc=dbaluta@ixiacom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®