mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ian Munsie <imunsie@au1.ibm.com>, Mike Galbraith <efault@gmx.de>,
	Paul Mackerras <paulus@samba.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Stephane Eranian <eranian@google.com>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [GIT PULL 0/4] perf/core improvements
Date: Fri, 3 Dec 2010 00:00:09 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1012022358380.2653@localhost6.localdomain6> (raw)
In-Reply-To: <1291318772-30880-1-git-send-email-acme@infradead.org>

On Thu, 2 Dec 2010, Arnaldo Carvalho de Melo wrote:

> Hi Ingo,
> 
>         Please consider pulling after at least Ian and Peter acks it:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux-2.6 perf/core
> 
> 	Peter already acked a previous version of this, so I left his acked by
> there, this new one is much simpler than the first one he acked, so I think
> he'll be happy with this one as well, Peter?
> 
> 	I tested it using the perf tools built from what is in tip/perf/urgent
> and it works as expected, i.e. the new fields are just discarded since they are
> stashed as a trailer in the MMAP, FORK, etc events, so old tools process new
> perf.data files just fine.
> 
> 	Also the new tools works on older kernels, also tested.
> 
> 	Ian, if you prefer, please test it before Ingo merges it.

Did so. Have some odd fallout:

    tracepoint event: type 65535

    data->tid 2621441 data->pid 9

Investigating. Please wait

	       tglx


  parent reply	other threads:[~2010-12-02 23:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02 19:39 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
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 ` Thomas Gleixner [this message]
2010-12-03  0:44   ` [GIT PULL 0/4] perf/core improvements 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
  -- strict thread matches above, loose matches on Subject: below --
2010-08-10 21:53 Arnaldo Carvalho de Melo
2010-08-11  6:35 ` Ingo Molnar

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=alpine.LFD.2.00.1012022358380.2653@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=acme@infradead.org \
    --cc=efault@gmx.de \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=imunsie@au1.ibm.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

all inboxes | Powered by JetHome®