mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Eric B Munson <ebmunson@us.ibm.com>
Cc: linux-kernel@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: perf record and multiple events
Date: Thu, 18 Feb 2010 14:47:01 +0100	[thread overview]
Message-ID: <1266500821.26719.649.camel@laptop> (raw)
In-Reply-To: <20100217173822.GA4137@us.ibm.com>

On Wed, 2010-02-17 at 17:38 +0000, Eric B Munson wrote:
> While testing perf record I found that when multiple events are specified
> on the command line, i.e. perf record -e dTLB-misses -e cache-misses,
> the are lumped into a single category on output from perf report.  The
> same event specification gives two event categories when using perf stat.
> Is this working as expected or should I see seperate entries in the report
> for each event?

The tools currently lack support for this, but patches are welcome.


  reply	other threads:[~2010-02-18 13:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 17:38 Eric B Munson
2010-02-18 13:47 ` Peter Zijlstra [this message]
2010-02-18 17:06   ` Eric B Munson

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=1266500821.26719.649.camel@laptop \
    --to=peterz@infradead.org \
    --cc=acme@ghostprotocols.net \
    --cc=ebmunson@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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