linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] tools lib subcmd: Show parent options in help
Date: Thu, 22 Jun 2023 15:28:31 -0700	[thread overview]
Message-ID: <CAM9d7cgnOzVV7ww-+4N_mccgn9r_xYX1LeExgxDOo0x5NG=Zqw@mail.gmail.com> (raw)
In-Reply-To: <CAP-5=fWOji8vCQfO-y4HnmFk2k+F70BtGHTjCg6XyORNfYNcww@mail.gmail.com>

On Wed, Jun 21, 2023 at 12:05 AM Ian Rogers <irogers@google.com> wrote:
>
> On Thu, May 25, 2023 at 3:09 PM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > I've just realized that help message in a subcommand didn't show one
> > in the parent command.  Since the option parser understands the parent,
> > display code should do the same.  For example, `perf ftrace latency -h`
> > should show options in the `perf ftrace` command too.
> >
> > Before:
> >
> >   $ perf ftrace latency -h
> >
> >    Usage: perf ftrace [<options>] [<command>]
> >       or: perf ftrace [<options>] -- [<command>] [<options>]
> >       or: perf ftrace {trace|latency} [<options>] [<command>]
> >       or: perf ftrace {trace|latency} [<options>] -- [<command>] [<options>]
> >
> >       -b, --use-bpf         Use BPF to measure function latency
> >       -n, --use-nsec        Use nano-second histogram
> >       -T, --trace-funcs <func>
> >                             Show latency of given function
> >
> > After:
> >
> >   $ perf ftrace latency -h
> >
> >    Usage: perf ftrace [<options>] [<command>]
> >       or: perf ftrace [<options>] -- [<command>] [<options>]
> >       or: perf ftrace {trace|latency} [<options>] [<command>]
> >       or: perf ftrace {trace|latency} [<options>] -- [<command>] [<options>]
> >
> >       -a, --all-cpus        System-wide collection from all CPUs
> >       -b, --use-bpf         Use BPF to measure function latency
> >       -C, --cpu <cpu>       List of cpus to monitor
> >       -n, --use-nsec        Use nano-second histogram
> >       -p, --pid <pid>       Trace on existing process id
> >       -T, --trace-funcs <func>
> >                             Show latency of given function
> >       -v, --verbose         Be more verbose
> >           --tid <tid>       Trace on existing thread id (exclusive to --pid)
> >
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > ---
> >  tools/lib/subcmd/parse-options.c | 26 ++++++++++++++++++--------
> >  1 file changed, 18 insertions(+), 8 deletions(-)
> >
> > diff --git a/tools/lib/subcmd/parse-options.c b/tools/lib/subcmd/parse-options.c
> > index 9fa75943f2ed..41de97671c72 100644
> > --- a/tools/lib/subcmd/parse-options.c
> > +++ b/tools/lib/subcmd/parse-options.c
> > @@ -806,18 +806,28 @@ static int option__cmp(const void *va, const void *vb)
> >
> >  static struct option *options__order(const struct option *opts)
> >  {
> > -       int nr_opts = 0, nr_group = 0, len;
> > -       const struct option *o = opts;
> > -       struct option *opt, *ordered, *group;
> > +       int nr_opts = 0, nr_group = 0, nr_parent = 0, len;
> > +       const struct option *o, *p = opts;
> > +       struct option *opt, *ordered = NULL, *group;
> >
> > -       for (o = opts; o->type != OPTION_END; o++)
> > +retry:
>
> Why use "goto retry" and not compute the size with the parent upfront?

No specific reason, just followed the same pattern as in
parse_{short,long}_opt(). :)

>
> > +       for (o = p; o->type != OPTION_END; o++)
> >                 ++nr_opts;
> >
> > -       len = sizeof(*o) * (nr_opts + 1);
> > -       ordered = malloc(len);
> > -       if (!ordered)
> > +       len = sizeof(*o) * (nr_opts + !o->parent);
>
> It'd be nice to comment on why the "!o->parent" here.

What about this?

/* It needs a terminating NULL entry when there's no parent */

Thanks,
Namhyung


>
> Thanks,
> Ian
>
> > +       group = realloc(ordered, len);
> > +       if (!group)
> >                 goto out;
> > -       memcpy(ordered, opts, len);
> > +       ordered = group;
> > +       memcpy(&ordered[nr_parent], p, sizeof(*o) * (nr_opts - nr_parent));
> > +
> > +       if (o->parent) {
> > +               p = o->parent;
> > +               nr_parent = nr_opts;
> > +               goto retry;
> > +       }
> > +       /* copy the last OPTION_END */
> > +       memcpy(&ordered[nr_opts], o, sizeof(*o));
> >
> >         /* sort each option group individually */
> >         for (opt = group = ordered; opt->type != OPTION_END; opt++) {
> > --
> > 2.41.0.rc0.172.g3f132b7071-goog
> >

  reply	other threads:[~2023-06-22 22:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25 22:09 [PATCH] tools lib subcmd: Show parent options in help Namhyung Kim
2023-06-21  7:05 ` Ian Rogers
2023-06-22 22:28   ` Namhyung Kim [this message]
2023-06-23  0:56     ` Ian Rogers

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='CAM9d7cgnOzVV7ww-+4N_mccgn9r_xYX1LeExgxDOo0x5NG=Zqw@mail.gmail.com' \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).