All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Ian Munsie <imunsie@au1.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Stephane Eranian <eranian@google.com>
Subject: Re: [GIT PULL 0/4] perf/core improvements
Date: Fri, 3 Dec 2010 11:05:28 -0200	[thread overview]
Message-ID: <20101203130528.GB19363@ghostprotocols.net> (raw)
In-Reply-To: <1291356549-sup-6865@au1.ibm.com>

Em Fri, Dec 03, 2010 at 05:10:44PM +1100, Ian Munsie escreveu:
> Excerpts from Arnaldo Carvalho de Melo's message of Fri Dec 03 06:39:28 +1100 2010:
> >     Ian, if you prefer, please test it before Ingo merges it.
> 
> Have done so and just about finished rebasing my patches on top of these
> - I'll try to get them posted tonight. The bug I was working on is
> fixed, so I'm happy :)

Great!
 
> I haven't come across the bug that Thomas ran into, but then again I
> haven't been testing the non-perf parts of perf for this either.

I'll work on the problem related by Thomas today.
 
> Which reminds me, does anyone have a test suite for perf other than
> ./perf test?

Not that I know of, perf test is intended to be that, please consider
adding more tests :)

I want to do things like start a thread that will generate cache misses,
and then have a monitor thread measuring it, passing the test if it gets
into some range (its sampling after all), etc.

- Arnaldo

  reply	other threads:[~2010-12-03 13:05 UTC|newest]

Thread overview: 17+ 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
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 [this message]
  -- 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=20101203130528.GB19363@ghostprotocols.net \
    --to=acme@infradead.org \
    --cc=a.p.zijlstra@chello.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.