Skip to contentSkip to conversation

Documentation: update kmemleak architecture support info

PATCH In review Maxin B John 2 participants 2 messages Jun 9, 2011 – Jun 10, 2011 Documentation

lore
Share & tools
lore

Maxin B John

author
#0 lore raw

PATCH 1/1 Documentation: update kmemleak architecture support info

Kmemleak now supports s390 and mips too.

Signed-off-by Maxin B. John <[email protected]>

---

Documentation/kmemleak.txt +2 -1
index 090e6ee..82833ff 100644
@@ -11,7 +11,8 @@ 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.
+Kmemleak is supported on x86, arm, powerpc, sparc, sh, microblaze, tile,
+s390 and mips.
 
 Usage
 -----
#1 lore raw
Quoted 9 lines · Maxin B John

Kmemleak now supports s390 and mips too.

Signed-off-by Maxin B. John<[email protected]>

---

Documentation/kmemleak.txt +0 -0
index 090e6ee..82833ff 100644

Documentation/kmemleak.txt with the difference that the orphan objects are not freed but only · line 18

Quoted 9 lines
Documentation/kmemleak.txt +2 -1
@@ -11,7 +11,8 @@ 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.
+Kmemleak is supported on x86, arm, powerpc, sparc, sh, microblaze, tile,
+s390 and mips.
 
  Usage
  -----

Hello,

I am fine with this. What do you say about having
something generic like:

"Please check DEBUG_KMEMLEAK dependencies in lib/Kconfig.debug for supported platforms"

In this way, there's no need to update kememleak.txt everytime when a new platform is supported.

thanks,
Daniel.