public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Namhyung Kim <namhyung@kernel.org>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>,
	Namhyung Kim <namhyung.kim@lge.com>,
	LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
	David Ahern <dsahern@gmail.com>,
	Stephane Eranian <eranian@google.com>,
	Pekka Enberg <penberg@kernel.org>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [RFC/PATCH 1/2] perf script: Add --time-filter option
Date: Thu, 16 May 2013 15:09:34 +0200	[thread overview]
Message-ID: <20130516130934.GA9058@gmail.com> (raw)
In-Reply-To: <20130515135608.GF17814@two.firstfloor.org>


* Andi Kleen <andi@firstfloor.org> wrote:

> On Wed, May 15, 2013 at 06:23:58PM +0900, Namhyung Kim wrote:
> > From: Namhyung Kim <namhyung.kim@lge.com>
> > 
> > The --time-filter option is for limiting samples within a range of
> > time.  A time range looks like <time1>-<time2> and at most one of them
> > can be omitted.  For instance:
> 
> It would be more useful for report or inject than for script.

The 2/2 patch does it for report ...

> After all with a script it's trivial to do an own filter.

Utility features/shortcuts are almost always useful, especially if they 
span multiple tools.

Thanks,

	Ingo

  parent reply	other threads:[~2013-05-16 13:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15  9:23 [RFC/PATCH 1/2] perf script: Add --time-filter option Namhyung Kim
2013-05-15  9:23 ` [RFC/PATCH 2/2] perf report: " Namhyung Kim
2013-05-15 11:51   ` Stephane Eranian
2013-05-16  0:48     ` Namhyung Kim
2013-05-15 13:56 ` [RFC/PATCH 1/2] perf script: " Andi Kleen
2013-05-16  0:55   ` Namhyung Kim
2013-05-16 13:09   ` Ingo Molnar [this message]
2013-05-15 15:16 ` David Ahern
2013-05-16  1:56   ` Namhyung Kim
2013-05-16  2:42     ` David Ahern
2013-05-16  8:50       ` Namhyung Kim
2013-05-16 13:29         ` David Ahern

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=20130516130934.GA9058@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=andi@firstfloor.org \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung.kim@lge.com \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.org \
    --cc=penberg@kernel.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