From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Jiri Olsa <jolsa@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Andi Kleen <andi@firstfloor.org>,
Wang Nan <wangnan0@huawei.com>,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [RFC/PATCH 2/2] perf sched: Make common options cascading
Date: Tue, 25 Oct 2016 14:21:32 -0300 [thread overview]
Message-ID: <20161025172132.GD4543@kernel.org> (raw)
In-Reply-To: <20161024170332.GE31643@krava>
Em Mon, Oct 24, 2016 at 07:03:32PM +0200, Jiri Olsa escreveu:
> On Mon, Oct 24, 2016 at 12:00:03PM +0900, Namhyung Kim wrote:
> > The -i and -v options can be used in subcommands so enable cascading the
> > sched_options. This fixes the following inconvenience in 'perf sched':
> >
> > $ perf sched -i perf.data.sched map
> > ... (it works well) ...
> >
> > $ perf sched map -i perf.data.sched
> > Error: unknown switch `i'
> >
> > Usage: perf sched map [<options>]
> >
> > --color-cpus <cpus>
> > highlight given CPUs in map
> > --color-pids <pids>
> > highlight given pids in map
> > --compact map output in compact mode
> > --cpus <cpus> display given CPUs in map
> >
> > With this patch, the second command line works with the perf.data.sched
> > data file.
> >
> > Cc: Josh Poimboeuf <jpoimboe@redhat.com>
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
>
> good idea, I'll use it in c2c ;-)
>
> for both:
>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
Applied, I guess 'perf kvm' would be another user, to make it sane wrt
file_name, -i and -o being available for 'perf kvm record', etc.
- Arnaldo
next prev parent reply other threads:[~2016-10-25 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 3:00 [RFC/PATCH 1/2] tools lib subcmd: Suppport cascading options Namhyung Kim
2016-10-24 3:00 ` [RFC/PATCH 2/2] perf sched: Make common options cascading Namhyung Kim
2016-10-24 17:03 ` Jiri Olsa
2016-10-25 17:21 ` Arnaldo Carvalho de Melo [this message]
2016-10-25 21:27 ` Namhyung Kim
2016-10-28 17:45 ` [tip:perf/core] " tip-bot for Namhyung Kim
2016-10-28 17:44 ` [tip:perf/core] tools lib subcmd: Suppport cascading options tip-bot for Namhyung Kim
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=20161025172132.GD4543@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=wangnan0@huawei.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