linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	eranian@gmail.com, "Meadows,
	Lawrence F" <lawrence.f.meadows@intel.com>
Subject: Re: [PATCH 0/3] perf_event: enable overflow interrupts on KNC
Date: Wed, 17 Oct 2012 23:47:00 +0200	[thread overview]
Message-ID: <20121017214700.GA9851@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1210171614060.23685@vincent-weaver-1.um.maine.edu>


* Vince Weaver <vincent.weaver@maine.edu> wrote:

> 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.

Ok. As long as it's all identical I'd still be inclined to 
include it in v3.7, to reduce version skew. If the v3.7-rc1 
kernel won't even boot it's not like we'll be able to further 
regress it.

Thanks,

	Ingo

  reply	other threads:[~2012-10-17 21:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17 17:02 [PATCH 0/3] perf_event: enable overflow interrupts on KNC Vince Weaver
2012-10-17 17:03 ` [PATCH 1/3] Make KNC use full 40-bit width of counters Vince Weaver
2012-10-24 10:34   ` [tip:perf/urgent] perf/x86: Make Intel " tip-bot for Vince Weaver
2012-10-17 17:04 ` [PATCH 2/3] perf_event: Remove cpuc->enable check on KNC event enable/disable Vince Weaver
2012-10-24 10:35   ` [tip:perf/urgent] perf/x86: Remove cpuc-> enable check on Intl " tip-bot for Vince Weaver
2012-10-17 17:05 ` [PATCH 3/3] perf_event: Enable overflow on KNC with a custom knc_pmu_handle_irq() Vince Weaver
2012-10-24 10:36   ` [tip:perf/urgent] perf/x86: Enable overflow on Intel " tip-bot for Vince Weaver
2012-10-17 18:07 ` [PATCH 0/3] perf_event: enable overflow interrupts on KNC Ingo Molnar
2012-10-17 20:24   ` Vince Weaver
2012-10-17 21:47     ` Ingo Molnar [this message]
2012-10-18 17:54       ` Vince Weaver
2012-10-18 18:54         ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121017214700.GA9851@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=eranian@gmail.com \
    --cc=lawrence.f.meadows@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=vincent.weaver@maine.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).