lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 24 Nov 2009 13:25:24 +0800
From:	Li Zefan <lizf@...fujitsu.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Pekka Enberg <penberg@...helsinki.fi>,
	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>,
	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: [PATCH 0/5] perf kmem: Add more functions and show more statistics

List of new things:

- Add option "--raw-ip", to print raw ip instead of symbols.

- Sort the output by fragmentation by default, and support
  multi keys.

- Collect and show cross node allocation stats.

- Collect and show alloc/free ping-pong stats.

- And help file.

---
 tools/perf/Documentation/perf-kmem.txt |   44 ++++
 tools/perf/builtin-kmem.c              |  353 ++++++++++++++++++++++++++------
 tools/perf/command-list.txt            |    1 +
 3 files changed, 331 insertions(+), 67 deletions(-)


Pekka, do you think we can remove kmemtrace now?

With kmem trace events, low-level analyzing can be done using
ftrace, and high-level analyzing can be done using perf-kmem.

And chance is, more people may use and improve perf-kmem, and it
will be well-maintained within the perf infrastructure. On the
other hand, I guess few people use and contribute to kmemtrace-user.

BTW, seems kmemtrace-user doesn't work with ftrace. I got setfault:

	# ./kmemtraced
	Copying /proc/kallsyms...
	Logging... Press Control-C to stop.
	^CSegmentation fault


--
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