linux-kernel - Your action on perf bug report is requested was Re: Basic perf PMU support for Haswell v11

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: <20130501101041.GG17814@two.firstfloor.org>
Date:	Wed, 1 May 2013 12:10:41 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	mingo@...nel.org
Cc:	mingo@...e.hu, linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Your action on perf bug report is requested was Re: Basic perf PMU
 support for Haswell v11

> I found a similar system (not same stepping, but same model) and tested
> perf top works fine here. Also on a couple of other systems.
> 
> Since I cannot reproduce I would need your help debugging it.

Ingo, I haven't heard back from you on this. 

You reported an unreproducable bug. I gave you several steps to
diagnose the problem, so that we can make progress on this.

You've had several days time now to to this, but I have not 
heard from you.

If you don't report back from 5/3/2013 I'll assume it was some
other mistake on your side.

As a reminder:

I assume it worked before my patches.  If you don't know
please double check. Also I assume there's no general
problem between the user land perf you used and the kernel.

The only patch I could think of which may affect other systems
is the moving of the APIC ack.

So does it work if you revert

 perf, x86: Move NMI clearing to end of PMI handler after ...

 If that is it we could white list it for Haswell.

If that's not it I may need a bisect, assuming the problem is stable.

Thanks for your cooperation.

-Andi
--
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/