mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@kernel.org, jolsa@kernel.org, mingo@kernel.org,
	peterz@infradead.org, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/2] perf, tools: Document event specifications better
Date: Tue, 22 Mar 2016 08:57:35 +0100	[thread overview]
Message-ID: <20160322075735.GA4473@krava.brq.redhat.com> (raw)
In-Reply-To: <1458575793-12091-1-git-send-email-andi@firstfloor.org>

On Mon, Mar 21, 2016 at 08:56:32AM -0700, Andi Kleen wrote:

SNIP

> +EVENT GROUPS
> +------------
> +
> +Perf supports time based multiplexing of events, when the number of events
> +active exceeds the number of hardware performance counters. Multiplexing
> +can cause measurement errors when the workload changes its execution
> +profile.
> +
> +When metrics are computed using formulas from event counts, it is useful to
> +ensure some events are always measured together as a group to minimize multiplexing
> +errors. Event groups can be specified using { }.
> +
> +  perf stat -e '{instructions,cycles}' ...
> +
> +When too many events are specified in the group perf the event will not
                                                   ^^^^^^^^^^^^^^
                                        maybe:    'none of them' will be meassured.



> +be measured. The number of available performance counters depend on the CPU.
> +For example Intel Core CPUs have typically four generic performance counters
> +for the core, plus a number of specialized fixed counters.
> +
> +Events from multiple different PMUs cannot be mixed in a group.

hum, but we allow that right?

only when there's mixture of SW and HW events we move
it all silently under HW event context

jirka

  parent reply	other threads:[~2016-03-22  7:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 15:56 Andi Kleen
2016-03-21 15:56 ` [PATCH 2/2] perf, tools: Fix documentation of :ppp in perf list Andi Kleen
2016-03-22  7:58   ` Jiri Olsa
2016-03-24  7:38   ` [tip:perf/urgent] perf list: Fix documentation of :ppp tip-bot for Andi Kleen
2016-03-22  7:57 ` Jiri Olsa [this message]
2016-03-22  8:47   ` [PATCH 1/2] perf, tools: Document event specifications better Peter Zijlstra
2016-03-22 18:09 Andi Kleen
2016-03-27 11:37 ` 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=20160322075735.GA4473@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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

Powered by JetHome