[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1210171614060.23685@vincent-weaver-1.um.maine.edu>
Date: Wed, 17 Oct 2012 16:24:02 -0400 (EDT)
From: Vince Weaver <vincent.weaver@...ne.edu>
To: Ingo Molnar <mingo@...nel.org>
cc: linux-kernel@...r.kernel.org,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
eranian@...il.com,
"Meadows, Lawrence F" <lawrence.f.meadows@...el.com>
Subject: Re: [PATCH 0/3] perf_event: enable overflow interrupts on KNC
On Wed, 17 Oct 2012, Ingo Molnar wrote:
> How well tested is this on real hardware and how robust is the
> hardware with this? Since it's a new PMU driver for v3.7, and if
> these are reasonably well tested, then we could send these to
> Linus via perf/urgent, so that they don't miss and have to wait
> all the way to v3.8.
You probably won't like this answer.
The patches have been tested against the 2.6.34 kernel that Intel provides
for KNC (found here http://software.intel.com/en-us/forums/topic/278102 )
perf stat, perf record, and PAPI have all been tested and work.
The patches I've sent are the 2.6.34 ones forward ported to the 3.7-rc1
kernel. I haven't been able to run a 3.7-rc kernel on the KNC board,
because there are other patches to mainline needed to get KNC running and
they'd all have to be forward-ported from 2.6.34.
Since the knc pmu driver closely models the p6 one, it was straightforward
to use it as a basis for the forward port. Everything _should_ work but
I've only compile tested.
Vince
vincent.weaver@...ne.edu
--
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