public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Munsie <imunsie@au1.ibm.com>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Mike Galbraith <efault@gmx.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>,
	Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 2/4] perf events: Make sample_type identity fields available in all PERF_RECORD_ events
Date: Fri, 03 Dec 2010 16:45:10 +1100	[thread overview]
Message-ID: <1291354847-sup-5582@au1.ibm.com> (raw)
In-Reply-To: <1291318772-30880-3-git-send-email-acme@infradead.org>

>      /*
> +     * If perf_event_attr.sample_id_all is set then all event types will
> +     * have the sample_type selected fields related to where/when
> +     * (identity) an event took place (TID, TIME, ID, CPU, STREAM_ID)
> +     * described in PERF_RECORD_SAMPLE below, it will be stashed just after
> +     * the perf_event_header and the fields already present for the existing
> +     * fields, i.e. at the end of the payload. That way a newer perf.data
> +     * file will be supported by older perf tools, with these new optional
> +     * fields being ignored.

I'd put a comment in each event to be clear, but this is fine too.

> @@ -3944,8 +3988,15 @@ static void perf_event_comm_output(struct perf_event *event,
>                       struct perf_comm_event *comm_event)
>  {
>      struct perf_output_handle handle;
> +    struct perf_sample_data sample;
>      int size = comm_event->event_id.header.size;
> -    int ret = perf_output_begin(&handle, event, size, 0, 0);
> +    int ret;

How about:

-    int size = comm_event->event_id.header.size;
-    int ret = perf_output_begin(&handle, event, size, 0, 0);
+    int size, ret;

Like you did for perf_event_mmap_output?


Other than that:

Acked-by: Ian Munsie <imunsie@au1.ibm.com>

  reply	other threads:[~2010-12-03  5:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02 19:39 [GIT PULL 0/4] perf/core improvements Arnaldo Carvalho de Melo
2010-12-02 19:39 ` [PATCH 1/4] perf events: Separate the routines handling the PERF_SAMPLE_ identity fields Arnaldo Carvalho de Melo
2010-12-03  5:40   ` Ian Munsie
2010-12-02 19:39 ` [PATCH 2/4] perf events: Make sample_type identity fields available in all PERF_RECORD_ events Arnaldo Carvalho de Melo
2010-12-03  5:45   ` Ian Munsie [this message]
2010-12-02 19:39 ` [PATCH 3/4] perf session: Parse sample earlier Arnaldo Carvalho de Melo
2010-12-03  5:46   ` Ian Munsie
2010-12-02 19:39 ` [PATCH 4/4] perf tools: Ask for ID PERF_SAMPLE_ info on all PERF_RECORD_ events Arnaldo Carvalho de Melo
2010-12-03  6:04   ` Ian Munsie
2010-12-02 23:00 ` [GIT PULL 0/4] perf/core improvements Thomas Gleixner
2010-12-03  0:44   ` Arnaldo Carvalho de Melo
2010-12-03 11:51     ` Thomas Gleixner
2010-12-07  6:54       ` [tip:perf/core] perf events: Fix event inherit fallout of precalculated headers tip-bot for Thomas Gleixner
2010-12-03  6:10 ` [GIT PULL 0/4] perf/core improvements Ian Munsie
2010-12-03 13:05   ` Arnaldo Carvalho de Melo

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=1291354847-sup-5582@au1.ibm.com \
    --to=imunsie@au1.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@infradead.org \
    --cc=acme@redhat.com \
    --cc=efault@gmx.de \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.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