public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric B Munson <ebmunson@us.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: paulus@samba.org, mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] Add ID and STREAM_ID to recorded event data
Date: Wed, 3 Mar 2010 12:09:20 +0000	[thread overview]
Message-ID: <20100303120920.GA3502@us.ibm.com> (raw)
In-Reply-To: <1267541905.25158.64.camel@laptop>

[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]

On Tue, 02 Mar 2010, Peter Zijlstra wrote:

> On Tue, 2010-03-02 at 14:42 +0000, Eric B Munson wrote:
> > Currently perf record does not write the ID or the STREAM_ID to disk
> > for events.  This doesn't allow report to tell if an event stream contains
> > one or more types of events.  This patch adds these two entries to the list
> > of data that record will write to disk.
> > 
> > Signed-off-by: Eric B Munson <ebmunson@us.ibm.com>
> > ---
> >  tools/perf/builtin-record.c |    3 ++-
> >  1 files changed, 2 insertions(+), 1 deletions(-)
> > 
> > diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> > index 771533c..35e4605 100644
> > --- a/tools/perf/builtin-record.c
> > +++ b/tools/perf/builtin-record.c
> > @@ -242,7 +242,8 @@ static void create_counter(int counter, int cpu, pid_t pid)
> >  				  PERF_FORMAT_TOTAL_TIME_RUNNING |
> >  				  PERF_FORMAT_ID;
> >  
> > -	attr->sample_type	|= PERF_SAMPLE_IP | PERF_SAMPLE_TID;
> > +	attr->sample_type	|= PERF_SAMPLE_IP | PERF_SAMPLE_TID |
> > +				   PERF_SAMPLE_ID | PERF_SAMPLE_STREAM_ID;
> >  
> >  	if (freq) {
> >  		attr->sample_type	|= PERF_SAMPLE_PERIOD;
> 
> can we make this conditional on there being more than one event, that
> saves a little space/time when recording
> 

The downside to this is report cannot print the name of the event being monitored
if we do not record the sample and stream id.  This is as report behaves currently
and if that is okay then I will put out V2 with that included today.

-- 
Eric B Munson
IBM Linux Technology Center
ebmunson@us.ibm.com


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2010-03-03 12:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 14:42 [PATCH 0/5] [RFC] Add multiple event support to perf report Eric B Munson
2010-03-02 14:42 ` [PATCH 1/5] Add ID and STREAM_ID to recorded event data Eric B Munson
2010-03-02 14:58   ` Peter Zijlstra
2010-03-02 15:18     ` Eric B Munson
2010-03-03 12:09     ` Eric B Munson [this message]
2010-03-03 12:17       ` Peter Zijlstra
2010-03-02 14:42 ` [PATCH 2/5] Change add_hist_entry to take the tree root instead of session Eric B Munson
2010-03-02 14:42 ` [PATCH 3/5] Add storage for seperating event types in report Eric B Munson
2010-03-02 14:42 ` [PATCH 4/5] Change perf_session post processing functions to take histogram tree Eric B Munson
2010-03-02 14:42 ` [PATCH 5/5] Add multiple event support to perf report 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=20100303120920.GA3502@us.ibm.com \
    --to=ebmunson@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.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