linux-kernel - Re: [PATCH 0/4] perf: memory load/store events generalization

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: <CABPqkBQP7VNZBFj2h_TA67rr_QL7oxj1p8CjzG+faBd2m0dQig@mail.gmail.com>
Date:	Fri, 22 Jul 2011 14:14:26 -0700
From:	Stephane Eranian <eranian@...gle.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Lin Ming <ming.m.lin@...el.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...e.hu>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] perf: memory load/store events generalization

On Fri, Jul 22, 2011 at 2:01 PM, Andi Kleen <andi@...stfloor.org> wrote:
>> That looks okay as a first approach tool. But what people are most
>> often interested in is to see where the misses occur, i.e., you need
>> to display load/store addresses somehow, especially for the more
>
> But that's what it already does?  (for loads, stores
> are not in there yet) Did you try it?
>
I meant displaying the load + data addresses.
I have not tried it yet, just looked at the patches.

> Or did you mean resolving the addresses? While I agree that would
> be useful that's a quite big task and I don't think it should
> be blocked on that.
>
I agree with you, just wanted to check on the longer term goal.
--
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/