[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130426225235.GI16732@two.firstfloor.org>
Date: Sat, 27 Apr 2013 00:52:35 +0200
From: Andi Kleen <andi@...stfloor.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Andi Kleen <andi@...stfloor.org>, 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: Re: Basic perf PMU support for Haswell v11
> How well was this
> patch-set tested on non-Haswell hardware, which makes up 99.99% of our
> installed base?
I tested on a couple systems now and then: usually Haswell, IvyBridge,
sometimes also Westmere and Atom. I don't retest every iteration,
as you know most of the changes you're requesting don't affect
the binary.
My test bed is likely to be smaller than yours though and as usual
as you well know some part of the kernel QA is after release.
>
> In particular, after applying your patches, 'perf top' stopped working on
> an Intel testbox of mine:
>
> processor : 15
> vendor_id : GenuineIntel
> cpu family : 6
> model : 26
> model name : Intel(R) Xeon(R) CPU X55600 @ 2.80GHz
I assume the second 0 is a typo?
> stepping : 5
> 'perf top' just does not produce any profiling output - it says 0 events.
Thanks for testing.
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.
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.
-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/
Powered by blists - more mailing lists