From: Daniel Baluta <dbaluta@ixiacom.com>
To: catalin.marinas@arm.com, rdunlap@xenotime.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Baluta <dbaluta@ixiacom.com>
Subject: [PATCH] kmemleak: update documentation
Date: Thu, 24 Mar 2011 16:49:33 +0200 [thread overview]
Message-ID: <1300978173-9983-1-git-send-email-dbaluta@ixiacom.com> (raw)
Besides x86 and arm, kmemleak now supports powerpc, sparc, sh,
microblaze and tile.
Signed-off-by: Daniel Baluta <dbaluta@ixiacom.com>
---
Documentation/kmemleak.txt | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/kmemleak.txt b/Documentation/kmemleak.txt
index 34f6638..090e6ee 100644
--- a/Documentation/kmemleak.txt
+++ b/Documentation/kmemleak.txt
@@ -11,6 +11,7 @@ with the difference that the orphan objects are not freed but only
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 cases in the init_call functions),
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.
--
1.7.1
next reply other threads:[~2011-03-24 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 14:49 Daniel Baluta [this message]
2011-03-24 15:49 ` Catalin Marinas
2011-03-24 21:26 ` Randy Dunlap
2011-03-29 7:36 ` Heiko Carstens
2011-03-29 7:51 ` Daniel Baluta
2011-03-29 9:41 ` Maxin John
2011-03-29 11:24 ` Daniel Baluta
2011-03-29 15:33 ` 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=1300978173-9983-1-git-send-email-dbaluta@ixiacom.com \
--to=dbaluta@ixiacom.com \
--cc=catalin.marinas@arm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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®