linux-kernel - Re: [Questions] perf c2c: What's the current status of perf c2c?

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]

Message-ID: <20151209105809.GE6373@twins.programming.kicks-ass.net>
Date:	Wed, 9 Dec 2015 11:58:09 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Jiri Olsa <jolsa@...hat.com>
Cc:	Yunlong Song <yunlong.song@...wei.com>, dzickus@...hat.com,
	dsahern@...il.com, fweisbec@...il.com, jmario@...hat.com,
	efault@....de, paulus@...ba.org, rfowles@...hat.com,
	eranian@...gle.com,
	"acme@...nel.org >> Arnaldo Carvalho de Melo" <acme@...nel.org>,
	mingo@...hat.com,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jiri Olsa <jolsa@...nel.org>,
	"wangnan0@...wei.com >> Wang Nan" <wangnan0@...wei.com>,
	fowles@...each.com, Namhyung Kim <namhyung@...nel.org>,
	andi@...stfloor.org
Subject: Re: [Questions] perf c2c: What's the current status of perf c2c?

On Wed, Dec 09, 2015 at 10:34:02AM +0100, Peter Zijlstra wrote:
> Which we can imagine could result in code like:
> 
> foobar:
> 	mov (%rax), %rax	# load bar::foo
> 	mov (%rax,1,4), %rax	# load foo::val
> 
> 
> And DWARFs should know this, so by knowing the instruction we can know
> which load missed the cache.
> 
> Once you have this information, you can use pahole like structure output
> and heat colour them or whatnot. Bright red if you miss lots etc..
> 
> Now currently this is possible but a bit of work because the DWARF
> annotations are not exactly following these data types, that is you
> might need to decode previous instructions and infer some bits.

To clarify, current DWARFs might only know the argument to foobar is of
type struct bar *, and we'll have to infer the rest.

> I think Stephane was working with GCC people to allow more/better DWARF
> annotations and allow easier retrieval of this information.

And even if that gets sorted, it might still make sense to implement the
hard case as per the above, because it'll take a long time before
everything is build with the fancy new GCC/dwarf output.
--
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/