From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Nick Forrington <nick.forrington@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH 2/2] perf lock info: Enforce exactly one of --map and --thread
Date: Tue, 31 Oct 2023 12:38:05 -0300 [thread overview]
Message-ID: <ZUEfXU34ZijKe8aA@kernel.org> (raw)
In-Reply-To: <20231031120526.11502-3-nick.forrington@arm.com>
Em Tue, Oct 31, 2023 at 12:05:25PM +0000, Nick Forrington escreveu:
> Improve error reporting for command line arguments.
>
> Display error/usage if neither --map or --thread are specified (rather
> than a non user-friendly error "Unknown type of information").
>
> Display error/usage if both --map and --thread are specified (rather
> than ignoring "--map" and displaying only thread information).
Shouldn't one of them be the default so that we type less for the most
common usage?
- Arnaldo
> Signed-off-by: Nick Forrington <nick.forrington@arm.com>
> ---
> tools/perf/builtin-lock.c | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/tools/perf/builtin-lock.c b/tools/perf/builtin-lock.c
> index 3aa8ba5ad928..cf29f648d291 100644
> --- a/tools/perf/builtin-lock.c
> +++ b/tools/perf/builtin-lock.c
> @@ -2021,6 +2021,27 @@ static int check_lock_report_options(const struct option *options,
> return 0;
> }
>
> +static int check_lock_info_options(const struct option *options,
> + const char * const *usage)
> +{
> + if (!info_map && !info_threads) {
> + pr_err("Requires one of --map or --threads\n");
> + parse_options_usage(usage, options, "map", 0);
> + parse_options_usage(NULL, options, "threads", 0);
> + return -1;
> +
> + }
> +
> + if (info_map && info_threads) {
> + pr_err("Cannot show map and threads together\n");
> + parse_options_usage(usage, options, "map", 0);
> + parse_options_usage(NULL, options, "threads", 0);
> + return -1;
> + }
> +
> + return 0;
> +}
> +
> static int check_lock_contention_options(const struct option *options,
> const char * const *usage)
>
> @@ -2709,6 +2730,10 @@ int cmd_lock(int argc, const char **argv)
> if (argc)
> usage_with_options(info_usage, info_options);
> }
> +
> + if (check_lock_info_options(info_options, info_usage) < 0)
> + return -1;
> +
> /* recycling report_lock_ops */
> trace_handler = &report_lock_ops;
> rc = __cmd_report(true);
> --
> 2.42.0
>
>
--
- Arnaldo
next prev parent reply other threads:[~2023-10-31 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 12:05 [PATCH 0/2] Perf lock improvements Nick Forrington
2023-10-31 12:05 ` [PATCH 1/2] perf lock report: Restore aggregation by caller by default Nick Forrington
2023-10-31 16:05 ` James Clark
2023-11-02 5:55 ` Namhyung Kim
2023-11-10 17:01 ` Nick Forrington
2023-10-31 12:05 ` [PATCH 2/2] perf lock info: Enforce exactly one of --map and --thread Nick Forrington
2023-10-31 15:38 ` Arnaldo Carvalho de Melo [this message]
2023-11-01 14:35 ` Nick Forrington
2023-11-02 6:00 ` Namhyung Kim
2023-11-08 20:28 ` Arnaldo Carvalho de Melo
2023-11-13 11:50 ` Nick Forrington
2023-11-27 14:43 ` Arnaldo Carvalho de Melo
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=ZUEfXU34ZijKe8aA@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=nick.forrington@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.