All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"ak@linux.intel.com" <ak@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung.kim@lge.com>
Subject: Re: [PATCH v6 2/2] perf stat: add interval printing
Date: Mon, 28 Jan 2013 16:21:51 -0300	[thread overview]
Message-ID: <20130128192151.GC15351@infradead.org> (raw)
In-Reply-To: <CABPqkBS9yPGb3DOZv9qTULZrP+-8Zrbri99ZGBt7KopTfPWEfQ@mail.gmail.com>

Em Mon, Jan 28, 2013 at 07:26:17PM +0100, Stephane Eranian escreveu:
> On Mon, Jan 28, 2013 at 6:59 PM, Arnaldo Carvalho de Melo
> <acme@redhat.com> wrote:
> > Em Fri, Jan 25, 2013 at 04:21:11PM +0100, Stephane Eranian escreveu:
> >> On Fri, Jan 25, 2013 at 3:52 AM, Arnaldo Carvalho de Melo
> >> <acme@redhat.com> wrote:
> >> > Em Tue, Jan 22, 2013 at 02:18:52PM +0100, Stephane Eranian escreveu:
> >> >> This patch adds a new printing mode for perf stat.
> >> >> It allows internval printing. That means perf stat
> >> >> can now print event deltas at regular time interval.
> >> >> This is useful to detect phases in programs.
> >> >
> >> > This patch is not applying to my perf/core branch, does it depend on
> >> > some other outstanding patchset from you?
> >> >
> >> > Tomorrow probably all I had in this area will be in Ingo's tree, but
> >> > can you please take a look at my perf/core branch at:
> >> >
> >> > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux
> >> >
> >> My patches are always relative to:
> >> git://git.kernel.org/pub/scm/linux/kernel/git/tip.tip.git
> >>
> >> Do you still need to rebase against your tree?
> >
> > Well, userspace code normally is developed on my tree and eventually
> > goes to the one you mentioned. If you make sure that now, that both are
> > synched after some weeks, then probably it'll work with my tree.
> >
> How's the kernel proper side of your tree sync'd with tip.git? I cannot have
> the kernel patches for one tree and the perf patches for another. That's a
> lot of overhead especially when it comes to testing.

Normally regularly, right now it seems all is synched.

- Arnaldo

  reply	other threads:[~2013-01-28 19:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 13:18 [PATCH v6 0/2] perf stat: add interval counter printing Stephane Eranian
2013-01-22 13:18 ` [PATCH v6 1/2] perf tools: add evsel prev_raw_count field Stephane Eranian
2013-01-22 13:18 ` [PATCH v6 2/2] perf stat: add interval printing Stephane Eranian
2013-01-24  9:39   ` Ingo Molnar
2013-01-25  2:52   ` Arnaldo Carvalho de Melo
2013-01-25 15:21     ` Stephane Eranian
2013-01-28 17:59       ` Arnaldo Carvalho de Melo
2013-01-28 18:26         ` Stephane Eranian
2013-01-28 19:21           ` Arnaldo Carvalho de Melo [this message]
2013-01-28 22:45             ` Stephane Eranian
2013-01-29  1:41               ` Arnaldo Carvalho de Melo
2013-01-29 11:48                 ` Stephane Eranian
2013-01-29 20:58                   ` 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=20130128192151.GC15351@infradead.org \
    --to=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=namhyung.kim@lge.com \
    --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 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.