diff options
author | Luis R. Rodriguez <lrodriguez@Atheros.com> | 2009-09-04 17:44:51 -0700 |
---|---|---|
committer | Catalin Marinas <catalin.marinas@arm.com> | 2009-09-08 16:36:08 +0100 |
commit | 30b3710105be0ba6bbdb7d7d126af76246b02eba (patch) | |
tree | 84200b02f8230f3706744512bf4ba68341d9b889 /README | |
parent | 4a558dd6f93d419cd318958577e25492bd09e960 (diff) | |
download | op-kernel-dev-30b3710105be0ba6bbdb7d7d126af76246b02eba.zip op-kernel-dev-30b3710105be0ba6bbdb7d7d126af76246b02eba.tar.gz |
kmemleak: add clear command support
In an ideal world your kmemleak output will be small, when its
not (usually during initial bootup) you can use the clear command
to ingore previously reported and unreferenced kmemleak objects. We
do this by painting all currently reported unreferenced objects grey.
We paint them grey instead of black to allow future scans on the same
objects as such objects could still potentially reference newly
allocated objects in the future.
To test a critical section on demand with a clean
/sys/kernel/debug/kmemleak you can do:
echo clear > /sys/kernel/debug/kmemleak
test your kernel or modules
echo scan > /sys/kernel/debug/kmemleak
Then as usual to get your report with:
cat /sys/kernel/debug/kmemleak
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions