linux-kernel - Re: [patch 0/4] perf_counter tools: support annotation of live kernel modules

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 2 Jul 2009 08:47:12 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Mike Galbraith <efault@....de>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Paul Mackerras <paulus@...ba.org>,
	Frédéric Weisbecker <fweisbec@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [patch 0/4] perf_counter tools: support annotation of live
	kernel modules


* Mike Galbraith <efault@....de> wrote:

> Per $subject, this patch set only supports for the LIVE kernel.  
> It adds support infrastructure for path discovery, load address 
> lookup, and symbol generation of live kernel modules.
> 
> TODO includes resurrection of live annotation in perf top, and 
> support for annotation and report generation of other than live 
> modules.  As the patch set sits, Perf top can generate symbols 
> from live binaries, but there's no live annotation capability yet.
> 
> patch1: perf_counter tools: Make symbol loading consistently return number of loaded symbols.
> patch2: perf_counter tools: Add infrastructure to support loading of kernel module symbols
> patch3: perf_counter tools: connect module support infrastructure to symbol loading infrastructure
> patch4: perf_counter tools: Enable kernel module symbol loading in tools
> 
> Comments and suggestions most welcome.

Looks very nice! I've applied it with a few minor stylistic fixlets 
and a tad more verbose changelogs.

I'm wondering about the next step: couldnt we somehow guess at the 
position of the vmlinux too, validate somehow that it corresponds to 
the kernel we are running - and then use it automatically and by 
default?

Plus, offline analysis would be nice as well i suspect - being able 
to look at profiles on a different box?

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