From: Namhyung Kim <namhyung@kernel.org>
To: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>,
Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
Chen Yu <yu.c.chen@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
acme@redhat.com, Fernand Sieber <sieberf@amazon.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 3/3] perf sched map: Add --fuzzy-name option for fuzzy matching in task names
Date: Thu, 27 Jun 2024 16:39:01 -0700 [thread overview]
Message-ID: <Zn34FZxPLh3llxy9@google.com> (raw)
In-Reply-To: <20240626091550.46707-4-vineethr@linux.ibm.com>
On Wed, Jun 26, 2024 at 02:45:50PM +0530, Madadi Vineeth Reddy wrote:
> The --fuzzy-name option can be used if fuzzy name matching is required.
> For example, "taskname" can be matched to any string that contains
> "taskname" as its substring.
>
> Sample output for --task-name wdav --fuzzy-name
> =============
> . *A0 . . . . - . 131040.641346 secs A0 => wdavdaemon:62509
> . A0 *B0 . . . - . 131040.641378 secs B0 => wdavdaemon:62274
> - *- - - - - - - 131040.641379 secs
- *- B0 - - - - - 131040.641379 secs
> *C0 . B0 . . . . . 131040.641572 secs C0 => wdavdaemon:62283
> C0 . B0 . *D0 . . . 131040.641572 secs D0 => wdavdaemon:62277
> C0 . B0 . D0 . *E0 . 131040.641578 secs E0 => wdavdaemon:62270
> *- - - - - - - - 131040.641581 secs
*- - B0 - D0 - E0 - 131040.641581 secs
Thanks,
Namhyung
>
> Suggested-by: Chen Yu <yu.c.chen@intel.com>
> Reviewed-and-tested-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
> Signed-off-by: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
> ---
> tools/perf/Documentation/perf-sched.txt | 3 +++
> tools/perf/builtin-sched.c | 22 +++++++++++++++-------
> 2 files changed, 18 insertions(+), 7 deletions(-)
>
> diff --git a/tools/perf/Documentation/perf-sched.txt b/tools/perf/Documentation/perf-sched.txt
> index 3095e280eb92..938b41a3befa 100644
> --- a/tools/perf/Documentation/perf-sched.txt
> +++ b/tools/perf/Documentation/perf-sched.txt
> @@ -137,6 +137,9 @@ OPTIONS for 'perf sched map'
> task name(s).
> ('-' indicates other tasks while '.' is idle).
>
> +--fuzzy-name::
> + Given task name(s) can be partially matched (fuzzy matching).
> +
> OPTIONS for 'perf sched timehist'
> ---------------------------------
> -k::
> diff --git a/tools/perf/builtin-sched.c b/tools/perf/builtin-sched.c
> index ecb43deb9d74..c801c38e8b9a 100644
> --- a/tools/perf/builtin-sched.c
> +++ b/tools/perf/builtin-sched.c
> @@ -157,6 +157,7 @@ struct perf_sched_map {
> struct perf_cpu_map *color_cpus;
> const char *color_cpus_str;
> const char *task_name;
> + bool fuzzy;
> struct perf_cpu_map *cpus;
> const char *cpus_str;
> };
> @@ -1599,12 +1600,16 @@ static struct CommandList *parse_commands(const char *commands)
> return cmd_list;
> }
>
> -static bool sched_match_task(const char *comm_str, struct CommandList *cmd_list)
> +static bool sched_match_task(const char *comm_str, struct CommandList *cmd_list, bool fuzzy_match)
> {
> bool match_found = false;
>
> - for (int i = 0; i < cmd_list->command_count && !match_found; i++)
> - match_found = !strcmp(comm_str, cmd_list->command_list[i]);
> + for (int i = 0; i < cmd_list->command_count && !match_found; i++) {
> + if (fuzzy_match)
> + match_found = !!strstr(comm_str, cmd_list->command_list[i]);
> + else
> + match_found = !strcmp(comm_str, cmd_list->command_list[i]);
> + }
>
> return match_found;
> }
> @@ -1727,7 +1732,8 @@ static int map_switch_event(struct perf_sched *sched, struct evsel *evsel,
> */
> tr->shortname[0] = '.';
> tr->shortname[1] = ' ';
> - } else if (!sched->map.task_name || sched_match_task(str, cmd_list)) {
> + } else if (!sched->map.task_name || sched_match_task(str, cmd_list,
> + sched->map.fuzzy)) {
> tr->shortname[0] = sched->next_shortname1;
> tr->shortname[1] = sched->next_shortname2;
>
> @@ -1756,15 +1762,15 @@ static int map_switch_event(struct perf_sched *sched, struct evsel *evsel,
> * Check which of sched_in and sched_out matches the passed --task-name
> * arguments and call the corresponding print_sched_map.
> */
> - if (sched->map.task_name && !sched_match_task(str, cmd_list)) {
> - if (!sched_match_task(thread__comm_str(sched_out), cmd_list))
> + if (sched->map.task_name && !sched_match_task(str, cmd_list, sched->map.fuzzy)) {
> + if (!sched_match_task(thread__comm_str(sched_out), cmd_list, sched->map.fuzzy))
> goto out;
> else
> goto sched_out;
>
> } else {
> str = thread__comm_str(sched_out);
> - if (!(sched->map.task_name && !sched_match_task(str, cmd_list)))
> + if (!(sched->map.task_name && !sched_match_task(str, cmd_list, sched->map.fuzzy)))
> proceed = 1;
> }
>
> @@ -3707,6 +3713,8 @@ int cmd_sched(int argc, const char **argv)
> "display given CPUs in map"),
> OPT_STRING(0, "task-name", &sched.map.task_name, "task",
> "map output only for the given task name(s)."),
> + OPT_BOOLEAN(0, "fuzzy-name", &sched.map.fuzzy,
> + "given command name can be partially matched (fuzzy matching)"),
> OPT_PARENT(sched_options)
> };
> const struct option timehist_options[] = {
> --
> 2.43.2
>
next prev parent reply other threads:[~2024-06-27 23:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 9:15 [PATCH v5 0/3] Introduce --task-name and --fuzzy-name options in perf sched map Madadi Vineeth Reddy
2024-06-26 9:15 ` [PATCH v5 1/3] perf sched map: Add task-name option to filter the output map Madadi Vineeth Reddy
2024-06-27 23:13 ` Namhyung Kim
2024-06-30 6:32 ` Madadi Vineeth Reddy
2024-06-26 9:15 ` [PATCH v5 2/3] perf sched map: Add support for multiple task names using CSV Madadi Vineeth Reddy
2024-06-27 23:36 ` Namhyung Kim
2024-06-30 6:35 ` Madadi Vineeth Reddy
2024-06-26 9:15 ` [PATCH v5 3/3] perf sched map: Add --fuzzy-name option for fuzzy matching in task names Madadi Vineeth Reddy
2024-06-27 23:39 ` Namhyung Kim [this message]
2024-06-30 6:36 ` Madadi Vineeth Reddy
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=Zn34FZxPLh3llxy9@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sieberf@amazon.com \
--cc=vineethr@linux.ibm.com \
--cc=yu.c.chen@intel.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;
as well as URLs for NNTP newsgroup(s).