linux-kernel - Re: [PATCH 00/21] perf, c2c: Add new tool to analyze cacheline contention on NUMA systems

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:	Tue, 11 Feb 2014 11:52:17 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Stephane Eranian <eranian@...gle.com>
Cc:	Don Zickus <dzickus@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	LKML <linux-kernel@...r.kernel.org>,
	Jiri Olsa <jolsa@...hat.com>, Joe Mario <jmario@...hat.com>,
	Richard Fowles <fowles@...each.com>
Subject: Re: [PATCH 00/21] perf, c2c: Add new tool to analyze cacheline
 contention on NUMA systems

On Tue, Feb 11, 2014 at 11:35:45AM +0100, Stephane Eranian wrote:
> On Tue, Feb 11, 2014 at 8:14 AM, Peter Zijlstra <peterz@...radead.org> wrote:
> >
> > That blows; how much is missing?
> 
> They need to annotate load and stores. I asked for that feature a while ago.
> It will come.

And there is no way to deduce the information? We have type information
for all arguments and local variables, right? So we can follow that.

struct foo {
	int ponies;
	int moar_ponies;
};

struct bar {
	int my_ponies;
	struct foo *foo;
};

int moo(struct bar *bar)
{
	return bar->foo->moar_ponies;
}

Since we have the argument type, we can find the type for both loads,
the first load:

  *bar+8, we know is: struct foo * bar::foo
  *foo+4, we know is: int foo::moar_ponies

Or am I missing something?
--
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/