linux-kernel - perf top using /proc/kcore

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 linux-hardening linux-cve-announce 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]

Message-ID: <20131015020935.GB30662@ghostprotocols.net>
Date:	Mon, 14 Oct 2013 23:09:35 -0300
From:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
To:	Adrian Hunter <adrian.hunter@...el.com>
Cc:	David Ahern <dsahern@...il.com>, Jiri Olsa <jolsa@...hat.com>,
	Namhyung Kim <namhyung@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: perf top using /proc/kcore

Hi Adrian,

	While testing 'perf top -U' to reply a message in another thread
I noticed that ksm symbols appeared as '[kernel]', and only when I tried
'perf top -U -v' to look at the DSO long name I noticed that it was...
/proc/kcore.

	Question is: since we have access to /proc/modules, can't we
parse that, as when we have access to vmlinux, and recreate the mmaps,
etc, and see:

	[module]  symbol

	Instead of grouping everything into a single [kernel] bucket?

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