public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Stephane Eranian <eranian@google.com>
Cc: Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH] perf cgroups: Fix perf_cgroup_switch schedule in warning
Date: Tue, 02 Oct 2012 15:10:46 +0200	[thread overview]
Message-ID: <1349183446.7780.32.camel@twins> (raw)
In-Reply-To: <CABPqkBQvhUk=3OU4brv0LefZnRn2xSALA2-cVmE3A1wazDT=XA@mail.gmail.com>

On Tue, 2012-10-02 at 14:48 +0200, Stephane Eranian wrote:
> Not sure, I understand what active_pmu represents.

Its a 'random' pmu of those that share the cpuctx, exactly so you can
limit pmu iterations to those with unique cpuctx instances.

Its assigned when we create a cpuctx to the pmu creating it, its
re-assigned on pmu destruction (if that ever were to happen).

I realize the name isn't really helping but at the time I couldn't come
up with anything better :/

If you've got a good suggestion I'd be glad to rename it.

  reply	other threads:[~2012-10-02 13:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 11:42 [PATCH] perf cgroups: Fix perf_cgroup_switch schedule in warning Jiri Olsa
2012-10-02 11:53 ` Peter Zijlstra
2012-10-02 12:01   ` Stephane Eranian
2012-10-02 12:39   ` Jiri Olsa
2012-10-02 12:48     ` Stephane Eranian
2012-10-02 13:10       ` Peter Zijlstra [this message]
2012-10-02 13:34         ` Stephane Eranian
2012-10-02 13:46           ` Peter Zijlstra
2012-10-02 13:46           ` Peter Zijlstra
2012-10-02 14:18             ` Stephane Eranian
  -- strict thread matches above, loose matches on Subject: below --
2012-10-02 11:18 Jiri Olsa

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=1349183446.7780.32.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.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