public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org, fweisbec@gmail.com,
	a.p.zijlstra@chello.nl, mingo@elte.hu, acme@redhat.com
Subject: Re: [PATCH/FIX] perf-events: Put the per cpu state for intel_pmu too
Date: Thu, 11 Nov 2010 19:44:04 +0100	[thread overview]
Message-ID: <4CDC3974.3000506@linux.intel.com> (raw)
In-Reply-To: <AANLkTi=-OjDaz9iDm1aNYzeFsHmewTNnGBS8pRx1vfJT@mail.gmail.com>

On 11/11/2010 6:54 PM, Stephane Eranian wrote:
> On Thu, Nov 11, 2010 at 6:35 PM, Andi Kleen<andi@firstfloor.org>  wrote:
>> Small bug fix for the earlier offcore_response patch:
>> need to put the events for intel_pmu too, not only core_pmu.
>>
> You don't need it for core pmu, this is for Core Duo/Solo
> if I recall correctly.

It shouldn't matter because Core Duo doesn't have any per CPU resources, 
but
it seems more symetric to call it in any case.

It may make a difference if other users of the per CPU resource code get 
added.

-Andi


  reply	other threads:[~2010-11-11 18:44 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11 16:15 [PATCH 1/3] perf-events: Add support for supplementary event registers Andi Kleen
2010-11-11 16:15 ` [PATCH 2/3] perf: Add support for extra parameters for raw events Andi Kleen
2010-11-11 17:54   ` Corey Ashford
2010-11-11 18:39     ` Andi Kleen
2010-11-11 19:38       ` Corey Ashford
2010-11-11 19:49         ` Andi Kleen
2010-11-11 19:59           ` Peter Zijlstra
2010-11-11 20:12             ` Andi Kleen
2010-11-11 20:37               ` Peter Zijlstra
2010-11-12 10:27                 ` Andi Kleen
2010-11-12 10:49                   ` Stephane Eranian
2010-11-12 11:36                     ` Peter Zijlstra
2010-11-12 13:00                       ` Stephane Eranian
2010-11-12 13:21                         ` Peter Zijlstra
2010-11-12 14:03                           ` Stephane Eranian
2010-11-12 13:30                         ` Frederic Weisbecker
2010-11-12 15:00                           ` Stephane Eranian
2010-11-12 10:41                 ` Stephane Eranian
2010-11-12 10:48                   ` Peter Zijlstra
2010-11-12 10:39             ` Stephane Eranian
2010-11-12 10:48               ` Andi Kleen
2010-11-12 10:52                 ` Stephane Eranian
2010-11-12 10:56                   ` Stephane Eranian
2010-11-11 16:15 ` [PATCH 3/3] perf-events: Fix LLC-* events on Intel Nehalem/Westmere Andi Kleen
2010-11-11 17:35 ` [PATCH/FIX] perf-events: Put the per cpu state for intel_pmu too Andi Kleen
2010-11-11 17:54   ` Stephane Eranian
2010-11-11 18:44     ` Andi Kleen [this message]
2010-11-11 21:29       ` Stephane Eranian
2010-11-11 18:06 ` [PATCH 1/3] perf-events: Add support for supplementary event registers Stephane Eranian
2010-11-11 18:42   ` Andi Kleen
2010-11-11 19:09 ` Peter Zijlstra
2010-11-11 19:25   ` Andi Kleen
2010-11-11 19:36     ` Peter Zijlstra
2010-11-11 19:45       ` Andi Kleen
2010-11-11 19:49         ` Peter Zijlstra

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=4CDC3974.3000506@linux.intel.com \
    --to=ak@linux.intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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