linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: William Cohen <wcohen@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: Using perf with cgroups and containers
Date: Fri, 28 Nov 2014 19:00:15 +0100	[thread overview]
Message-ID: <20141128180015.GZ12538@two.firstfloor.org> (raw)
In-Reply-To: <54764629.9050601@redhat.com>

> Is there some where that explain use of the "{}" for event grouping? 

The only good description I know of is in the ucevent documentation.

https://github.com/andikleen/pmu-tools/tree/master/ucevent#grouping-event-scheduling-and-measurement-inaccuracy

Yes the documentation probably needs to be improved (as in many other
ways)

> 
>       -G name,..., --cgroup name,...
>            monitor only in the container (cgroup) called "name". This option
>            is available only in per-cpu mode. The cgroup filesystem must be
>            mounted. All threads belonging to container "name" are monitored
>            when they run on the monitored CPUs. Multiple cgroups can be
>            provided. Each cgroup is applied to the corresponding event, i.e.,
>            first cgroup to first event, second cgroup to second event and so
>            on. It is possible to provide an empty cgroup (monitor all the
>            time) using, e.g., -G foo,,bar. Cgroups must have corresponding
>            events, i.e., they always refer to events defined earlier on the
>            command line.
> 
> The results looks pretty questionable on my machine with the version of perf and kernel I am using:

You're right it doesn't work as I described. Should probably fix it,
my way would make a lot more sense :-)

I guess the current interface was more aimed at scripts.


-Andi
-- 
ak@linux.intel.com -- Speaking for myself only.

      reply	other threads:[~2014-11-28 18:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26 16:59 Using perf with cgroups and containers William Cohen
2014-11-26 20:52 ` Andi Kleen
2014-11-26 21:29   ` William Cohen
2014-11-28 18:00     ` Andi Kleen [this message]

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=20141128180015.GZ12538@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=wcohen@redhat.com \
    /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).