public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: tzanussi@gmail.com, linux-kernel@vger.kernel.org, fweisbec@gmail.com
Subject: Re: [PATCH 0/7] perf trace command-line cleanup
Date: Tue, 9 Nov 2010 16:38:29 -0500	[thread overview]
Message-ID: <20101109213829.GB7883@ghostprotocols.net> (raw)
In-Reply-To: <1289337502-2492-1-git-send-email-tzanussi@gmail.com>

Ingo,

	Please pull from Tom's git tree, I'm traveling and can't do
further tests, but all seems cool improvements,

Thanks a lot,

- Arnaldo

Em Tue, Nov 09, 2010 at 03:18:15PM -0600, tzanussi@gmail.com escreveu:
> From: Tom Zanussi <tom.zanussi@linux.intel.com>
> 
> There are currently some inconsistencies in perf trace command-line
> handling - for example, the system-wide param is hard-coded into the
> canned scripts, and the user doesn't have any option to avoid it.
> This patchset removes that limitation and cleans up some related
> complications introduced by live-mode.  It also more clearly documents
> usage, and fixes up a couple other minor problems.
> 
> This patchset can also be pulled from here:
> 
> git://github.com/zanussi/linux-2.6.git perf-trace-updates
> 
> 
> Tom Zanussi (7):
>   perf trace scripting: fix some small memory leaks and missing error
>     checks
>   perf trace scripting: remove system-wide param from shell scripts
>   perf record: make the record options available outside perf record
>   perf trace record: handle commands correctly
>   perf trace: live-mode command-line cleanup
>   perf trace: update Documentation with new perf trace variants
>   perf trace: update usage
> 
>  tools/perf/Documentation/perf-trace.txt            |   57 +++++-
>  tools/perf/builtin-record.c                        |   10 +-
>  tools/perf/builtin-trace.c                         |  209 ++++++++++++++------
>  tools/perf/scripts/perl/bin/failed-syscalls-record |    2 +-
>  tools/perf/scripts/perl/bin/rw-by-file-record      |    2 +-
>  tools/perf/scripts/perl/bin/rw-by-pid-record       |    2 +-
>  tools/perf/scripts/perl/bin/rwtop-record           |    2 +-
>  tools/perf/scripts/perl/bin/wakeup-latency-record  |    2 +-
>  tools/perf/scripts/perl/bin/workqueue-stats-record |    2 +-
>  .../python/bin/failed-syscalls-by-pid-record       |    2 +-
>  .../scripts/python/bin/futex-contention-record     |    2 +-
>  tools/perf/scripts/python/bin/netdev-times-record  |    2 +-
>  .../perf/scripts/python/bin/sched-migration-record |    2 +-
>  tools/perf/scripts/python/bin/sctop-record         |    2 +-
>  .../python/bin/syscall-counts-by-pid-record        |    2 +-
>  .../perf/scripts/python/bin/syscall-counts-record  |    2 +-
>  16 files changed, 217 insertions(+), 85 deletions(-)
> 
> -- 
> Tom Zanussi, Intel Open Source Technology Center

  parent reply	other threads:[~2010-11-10  5:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 21:18 [PATCH 0/7] perf trace command-line cleanup tzanussi
2010-11-09 21:18 ` [PATCH 1/7] perf trace scripting: fix some small memory leaks and missing error checks tzanussi
2010-11-09 21:18 ` [PATCH 2/7] perf trace scripting: remove system-wide param from shell scripts tzanussi
2010-11-09 21:18 ` [PATCH 3/7] perf record: make the record options available outside perf record tzanussi
2010-11-09 21:18 ` [PATCH 4/7] perf trace record: handle commands correctly tzanussi
2010-11-09 21:18 ` [PATCH 5/7] perf trace: live-mode command-line cleanup tzanussi
2010-11-09 21:18 ` [PATCH 6/7] perf trace: update Documentation with new perf trace variants tzanussi
2010-11-09 21:18 ` [PATCH 7/7] perf trace: update usage tzanussi
2010-11-09 21:38 ` Arnaldo Carvalho de Melo [this message]
2010-11-10  7:32   ` [PATCH 0/7] perf trace command-line cleanup Ingo Molnar
2010-11-10 18:09     ` Tom Zanussi

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=20101109213829.GB7883@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tzanussi@gmail.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