linux-kernel - Re: [PATCH 06/14] perf, x86: PEBS infrastructure

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: <bd4cb8901003051151s795839ddq67640fc9ad73c7bd@mail.gmail.com>
Date:	Fri, 5 Mar 2010 11:51:32 -0800
From:	Stephane Eranian <eranian@...gle.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Paul Mackerras <paulus@...ba.org>, mingo@...e.hu,
	linux-kernel@...r.kernel.org, robert.richter@....com,
	fweisbec@...il.com, Arnaldo Carvalho de Melo <acme@...radead.org>
Subject: Re: [PATCH 06/14] perf, x86: PEBS infrastructure

On Fri, Mar 5, 2010 at 11:39 AM, Peter Zijlstra <peterz@...radead.org> wrote:
> On Fri, 2010-03-05 at 11:11 -0800, Stephane Eranian wrote:
>> By rewinding you get the IP of the instruction that caused the event. But the
>> register state is STILL reflecting the situation at retirement of that
>> instruction.
>
> I'm quite aware of that, but its near impossible to reverse interpret
> instructions such as "mov rdx, $rdx", so until we get fault like PEBS
> we'll just have to live with this.
>
I am sure you are, but that's not necessarily true of everybody.
So this needs to be clearly spelled out in some documentation
about precise + your MISC_EXACT bit.
--
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/