public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jin Yao <yao.jin@linux.intel.com>
Cc: jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
	alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
	ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v1 0/8] perf: Follow-up patches to improve time slice
Date: Tue, 16 Jan 2018 11:48:44 -0300	[thread overview]
Message-ID: <20180116144844.GB16107@kernel.org> (raw)
In-Reply-To: <20180116115519.GA18544@krava>

Em Tue, Jan 16, 2018 at 12:55:19PM +0100, Jiri Olsa escreveu:
> On Wed, Jan 10, 2018 at 11:00:25PM +0800, Jin Yao wrote:
> > It's follow-up patches to improve the perf time slice feature
> > (perf report/script --time xxx)
> > 
> > 1. Improve the error message
> >    perf report: Improve error msg when no first/last sample time found
> >    perf script: Improve error msg when no first/last sample time found
> > 
> > 2. Fix an issue that illegal percent was accepted previously (e.g. 1abc%)
> >    perf util: Improve error checking for time percent input
> > 
> > 3. Omit the slice index if possible. For example,
> >    perf report --stdio --time 10%/1 is equivalent to
> >    perf report --stdio --time 10%
> > 
> >    perf util: Support no index time percent slice 
> > 
> > 4. Add indication of time slices in perf report header.
> >    perf report: Add an indication of what time slices are used
> > 
> > 5. Remove the time slices number limitation in perf report/script
> >    perf util: Allocate time slices buffer according to number of comma
> >    perf report: Remove the time slices number limitation
> >    perf script: Remove the time slices number limitation
> > 
> > Jin Yao (8):
> >   perf report: Improve error msg when no first/last sample time found
> >   perf script: Improve error msg when no first/last sample time found
> >   perf util: Improve error checking for time percent input
> >   perf util: Support no index time percent slice
> >   perf report: Add an indication of what time slices are used
> >   perf util: Allocate time slices buffer according to number of comma
> >   perf report: Remove the time slices number limitation
> >   perf script: Remove the time slices number limitation
> 
> from quick look it looks ok
> 
> Reviewed-by: Jiri Olsa <jolsa@redhat.com>

Thanks, applied, now test building with 'make -C tools/perf build-test',
containers, etc.

- Arnaldo

  parent reply	other threads:[~2018-01-16 14:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 15:00 [PATCH v1 0/8] perf: Follow-up patches to improve time slice Jin Yao
2018-01-10 15:00 ` [PATCH v1 1/8] perf report: Improve error msg when no first/last sample time found Jin Yao
2018-01-17 16:34   ` [tip:perf/core] " tip-bot for Jin Yao
2018-01-10 15:00 ` [PATCH v1 2/8] perf script: " Jin Yao
2018-01-17 16:35   ` [tip:perf/core] " tip-bot for Jin Yao
2018-01-10 15:00 ` [PATCH v1 3/8] perf util: Improve error checking for time percent input Jin Yao
2018-01-17 16:35   ` [tip:perf/core] " tip-bot for Jin Yao
2018-01-10 15:00 ` [PATCH v1 4/8] perf util: Support no index time percent slice Jin Yao
2018-01-17 16:36   ` [tip:perf/core] " tip-bot for Jin Yao
2018-01-10 15:00 ` [PATCH v1 5/8] perf report: Add an indication of what time slices are used Jin Yao
2018-01-17 16:36   ` [tip:perf/core] " tip-bot for Jin Yao
2018-01-10 15:00 ` [PATCH v1 6/8] perf util: Allocate time slices buffer according to number of comma Jin Yao
2018-01-17 16:37   ` [tip:perf/core] " tip-bot for Jin Yao
2018-01-10 15:00 ` [PATCH v1 7/8] perf report: Remove the time slices number limitation Jin Yao
2018-01-16 14:45   ` Arnaldo Carvalho de Melo
2018-01-17 16:37   ` [tip:perf/core] " tip-bot for Jin Yao
2018-01-10 15:00 ` [PATCH v1 8/8] perf script: " Jin Yao
2018-01-17 16:37   ` [tip:perf/core] " tip-bot for Jin Yao
2018-01-16 11:55 ` [PATCH v1 0/8] perf: Follow-up patches to improve time slice Jiri Olsa
2018-01-16 12:31   ` Jin, Yao
2018-01-16 14:48   ` Arnaldo Carvalho de Melo [this message]
2018-01-17  1:18     ` Jin, Yao

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=20180116144844.GB16107@kernel.org \
    --to=acme@kernel.org \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=yao.jin@intel.com \
    --cc=yao.jin@linux.intel.com \
    /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