public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"andi@firstfloor.org" <andi@firstfloor.org>,
	"acme@ghostprotocols.net" <acme@ghostprotocols.net>
Subject: Re: [PATCH] perf_event: fix Ming's Intel NHM/WSM/SNB uncore PMU patch
Date: Thu, 01 Sep 2011 20:38:42 +0800	[thread overview]
Message-ID: <1314880722.2867.4.camel@hp6530s> (raw)
In-Reply-To: <20110831124125.GA10443@quad>

On Wed, 2011-08-31 at 20:41 +0800, Stephane Eranian wrote:
> The following patch sits on top of Lin Ming's patch
> which adds support for Intel uncore PMU on NHM/WSM/SNB.
> The patch series was posted on LKML in July 2011.
> 
> The patches fixes:
>   - nhm_uncore_pmu_enable_all() to also enabled the fixed uncore counters
>   - uncore_pmu_add() to schedule for the actual max number of generic counters
>   - fixed the NHM/WSM vs. SNB MSRs for the fixed counter, they are swapped 
> 
> The patch adds the following improvement:
>   - add an event group validation function, to check if a group can ever be
>     schedule. This way, the behavior is consistent with core PMU event groups.
> 
> Signed-off-by: Stephane Eranian <eranian@google.com>

Can I merge this patch into my series with these change logs and your
signed-off-by?

Thanks,
Lin Ming


  reply	other threads:[~2011-09-01 12:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 12:41 [PATCH] perf_event: fix Ming's Intel NHM/WSM/SNB uncore PMU patch Stephane Eranian
2011-09-01 12:38 ` Lin Ming [this message]
2011-09-01 12:45   ` Stephane Eranian

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=1314880722.2867.4.camel@hp6530s \
    --to=ming.m.lin@intel.com \
    --cc=acme@ghostprotocols.net \
    --cc=andi@firstfloor.org \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    /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