linux-kernel - Re: [PATCH] perf, x86: Add workaround for MEM_*

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:	Mon, 6 May 2013 19:41:54 +0200
From:	Stephane Eranian <eranian@...gle.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Andi Kleen <andi@...stfloor.org>, "mingo@...e.hu" <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] perf, x86: Add workaround for MEM_*_RETIRED errata BV98

On Thu, May 2, 2013 at 9:32 AM, Peter Zijlstra <peterz@...radead.org> wrote:
> On Wed, May 01, 2013 at 09:21:55PM +0200, Stephane Eranian wrote:
>> On Wed, May 1, 2013 at 9:13 PM, Andi Kleen <andi@...stfloor.org> wrote:
>> >> Unfortunately, Andi's patch fails to correct the problem though
>> >> it is the right approach. As he said, the problem is unfortunately
>> >
>> > perf stat -a / record -a / top will work.
>> >
>> But it does not for perf stat -a. Look at my example, run it on your machine.
>
>
> Since nobody seems interested in explaining the exact nature of the hardware
> failure I think the best thing we can do is simply blacklist these events.
>
> Broken hardware is broken after all -- we should jump through too many hoops
> pretending its not.

Problem is, those events are really important. We need to be able to
measure them.
--
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/