From: Nick Forrington <nick.forrington@arm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
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>, 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: Mon, 13 Nov 2023 11:50:16 +0000 [thread overview]
Message-ID: <df428c93-e3b8-c60c-001f-2228845983cf@arm.com> (raw)
In-Reply-To: <ZUvvXhkY+NcSxaJU@kernel.org>
On 08/11/2023 20:28, Arnaldo Carvalho de Melo wrote:
> Em Wed, Nov 01, 2023 at 11:00:42PM -0700, Namhyung Kim escreveu:
>> On Wed, Nov 1, 2023 at 7:35 AM Nick Forrington <nick.forrington@arm.com> wrote:
>>>
>>> On 31/10/2023 15:38, Arnaldo Carvalho de Melo wrote:
>>>> 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
>>>>
>>> There isn't an obvious choice (to me) for which would be the default.
>>>
>>> Both options display completely different data/outputs, so I think it
>>> makes sense to be explicit about which data is requested.
>> Maybe we can default to display both. :)
> Yeah, that would be a better approach, I think.
>
> - Arnaldo
>
I'll submit an updated series for this, with the next update to patch 1/2
Thanks,
Nick
>> Thanks,
>> Namhyung
>>
>>>
>>> An alternative could be to use sub-commands e.g. "perf lock info
>>> threads" or just "perf lock threads", although changing the existing
>>> options would be more disruptive.
>>>
>>>
>>> Cheers,
>>> Nick
>>>
>>>>> 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
>>>>>
>>>>>
next prev parent reply other threads:[~2023-11-13 11:50 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
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 [this message]
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=df428c93-e3b8-c60c-001f-2228845983cf@arm.com \
--to=nick.forrington@arm.com \
--cc=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 \
/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
all inboxes | Powered by JetHome®