From: weilin.wang@intel.com
To: weilin.wang@intel.com, Ian Rogers <irogers@google.com>,
Kan Liang <kan.liang@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Perry Taylor <perry.taylor@intel.com>,
Samantha Alt <samantha.alt@intel.com>,
Caleb Biggers <caleb.biggers@intel.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: [RFC PATCH v4 13/15] perf stat: Code refactoring in hardware-grouping
Date: Thu, 8 Feb 2024 19:14:39 -0800 [thread overview]
Message-ID: <20240209031441.943012-14-weilin.wang@intel.com> (raw)
In-Reply-To: <20240209031441.943012-1-weilin.wang@intel.com>
From: Weilin Wang <weilin.wang@intel.com>
Decouple the step to generate final grouping strings out from the
build_grouping step so that we could do single metric grouping and then
merge groups if needed later.
Signed-off-by: Weilin Wang <weilin.wang@intel.com>
---
tools/perf/util/metricgroup.c | 50 +++++++++++++++++------------------
1 file changed, 25 insertions(+), 25 deletions(-)
diff --git a/tools/perf/util/metricgroup.c b/tools/perf/util/metricgroup.c
index f1eb73957765..cfdbb5f7fb77 100644
--- a/tools/perf/util/metricgroup.c
+++ b/tools/perf/util/metricgroup.c
@@ -1896,9 +1896,10 @@ static int find_and_set_counters(struct metricgroup__event_info *e,
{
int ret;
unsigned long find_bit = 0;
-
- if (e->taken_alone && current_group->taken_alone)
+ if (e->taken_alone && current_group->taken_alone) {
+ pr_debug("current group with taken alone event already\n");
return -ENOSPC;
+ }
if (e->free_counter)
return 0;
if (e->fixed_counter) {
@@ -2017,7 +2018,8 @@ static int assign_event_grouping(struct metricgroup__event_info *e,
list_for_each_entry(g, groups, nd) {
if (!strcasecmp(g->pmu_name, e->pmu_name)) {
- pr_debug("found group for event %s in pmu %s\n", e->name, g->pmu_name);
+ pr_debug("found group header for event %s in pmu %s\n",
+ e->name, g->pmu_name);
pmu_group_head = g;
break;
}
@@ -2146,26 +2148,22 @@ static int hw_aware_metricgroup__build_event_string(struct list_head *group_strs
*/
static int create_grouping(struct list_head *pmu_info_list,
struct list_head *event_info_list,
- struct list_head *groupings,
- const char *modifier)
+ struct list_head *grouping)
{
int ret = 0;
struct metricgroup__event_info *e;
- LIST_HEAD(groups);
char *bit_buf = malloc(NR_COUNTERS);
- //TODO: for each new core group, we should consider to add events that uses fixed counters
+ //TODO: for each new core group, we could consider to add events that
+ //uses fixed counters
list_for_each_entry(e, event_info_list, nd) {
bitmap_scnprintf(e->counters, NR_COUNTERS, bit_buf, NR_COUNTERS);
pr_debug("Event name %s, [pmu]=%s, [counters]=%s, [taken_alone]=%d\n",
e->name, e->pmu_name, bit_buf, e->taken_alone);
- ret = assign_event_grouping(e, pmu_info_list, &groups);
+ ret = assign_event_grouping(e, pmu_info_list, grouping);
if (ret)
- goto out;
+ return ret;
}
- ret = hw_aware_metricgroup__build_event_string(groupings, modifier, &groups);
-out:
- metricgroup__free_group_list(&groups);
return ret;
};
@@ -2186,9 +2184,8 @@ static bool is_special_event(const char *id)
* @groupings: header to the list of final event grouping.
* @modifier: any modifiers added to the events.
*/
-static int hw_aware_build_grouping(struct expr_parse_ctx *ctx __maybe_unused,
- struct list_head *groupings __maybe_unused,
- const char *modifier __maybe_unused)
+static int hw_aware_build_grouping(struct expr_parse_ctx *ctx,
+ struct list_head *grouping)
{
int ret = 0;
struct hashmap_entry *cur;
@@ -2220,8 +2217,7 @@ static int hw_aware_build_grouping(struct expr_parse_ctx *ctx __maybe_unused,
ret = get_pmu_counter_layouts(&pmu_info_list, ltable);
if (ret)
goto err_out;
- ret = create_grouping(&pmu_info_list, &event_info_list, groupings,
- modifier);
+ ret = create_grouping(&pmu_info_list, &event_info_list, grouping);
err_out:
metricgroup__free_event_info(&event_info_list);
@@ -2267,23 +2263,25 @@ static int hw_aware_parse_ids(struct perf_pmu *fake_pmu,
{
struct parse_events_error parse_error;
struct evlist *parsed_evlist;
- LIST_HEAD(groupings);
+ LIST_HEAD(grouping_str);
+ LIST_HEAD(grouping);
struct metricgroup__group_strs *group;
int ret;
*out_evlist = NULL;
- ret = hw_aware_build_grouping(ids, &groupings, modifier);
- if (ret) {
- metricgroup__free_grouping_strs(&groupings);
- return ret;
- }
+ ret = hw_aware_build_grouping(ids, &grouping);
+ if (ret)
+ goto out;
+ ret = hw_aware_metricgroup__build_event_string(&grouping_str, modifier, &grouping);
+ if (ret)
+ goto out;
parsed_evlist = evlist__new();
if (!parsed_evlist) {
ret = -ENOMEM;
goto err_out;
}
- list_for_each_entry(group, &groupings, nd) {
+ list_for_each_entry(group, &grouping_str, nd) {
struct strbuf *events = &group->grouping_str;
pr_debug("Parsing metric events '%s'\n", events->buf);
@@ -2303,7 +2301,9 @@ static int hw_aware_parse_ids(struct perf_pmu *fake_pmu,
err_out:
parse_events_error__exit(&parse_error);
evlist__delete(parsed_evlist);
- metricgroup__free_grouping_strs(&groupings);
+out:
+ metricgroup__free_group_list(&grouping);
+ metricgroup__free_grouping_strs(&grouping_str);
return ret;
}
--
2.42.0
next prev parent reply other threads:[~2024-02-09 3:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 3:14 [RFC PATCH v4 00/15] Perf stat metric grouping with hardware information weilin.wang
2024-02-09 3:14 ` [RFC PATCH v4 01/15] perf stat: Add new field in stat_config to enable hardware aware grouping weilin.wang
2024-02-09 3:14 ` [RFC PATCH v4 02/15] perf stat: Add basic functions for the " weilin.wang
2024-02-09 3:14 ` [RFC PATCH v4 03/15] perf pmu-events: Add functions in jevent.py to parse counter and event info for " weilin.wang
2024-03-24 4:49 ` Ian Rogers
2024-03-26 22:41 ` Wang, Weilin
2024-03-27 0:02 ` Ian Rogers
2024-02-09 3:14 ` [RFC PATCH v4 04/15] find_bit: add _find_last_and_bit() to support finding the most significant set bit weilin.wang
2024-03-24 4:19 ` Ian Rogers
2024-02-09 3:14 ` [RFC PATCH v4 05/15] perf stat: Add functions to set counter bitmaps for hardware-grouping method weilin.wang
2024-03-24 4:51 ` Ian Rogers
2024-02-09 3:14 ` [RFC PATCH v4 06/15] perf stat: Add functions to get counter info weilin.wang
2024-03-24 4:58 ` Ian Rogers
2024-02-09 3:14 ` [RFC PATCH v4 07/15] perf stat: Add functions to create new group and assign events into groups weilin.wang
2024-03-24 5:00 ` Ian Rogers
2024-02-09 3:14 ` [RFC PATCH v4 08/15] perf stat: Add build string function and topdown events handling in hardware-grouping weilin.wang
2024-02-09 3:14 ` [RFC PATCH v4 09/15] perf stat: Add function to handle special events " weilin.wang
2024-03-24 5:20 ` Ian Rogers
2024-02-09 3:14 ` [RFC PATCH v4 10/15] perf stat: Add function to combine metrics for hardware-grouping weilin.wang
2024-02-09 3:14 ` [RFC PATCH v4 11/15] perf stat: Handle taken alone in hardware-grouping weilin.wang
2024-03-24 5:24 ` Ian Rogers
2024-03-26 23:06 ` Wang, Weilin
2024-03-27 0:05 ` Ian Rogers
2024-03-27 0:40 ` Wang, Weilin
2024-02-09 3:14 ` [RFC PATCH v4 12/15] perf stat: Handle NMI " weilin.wang
2024-03-24 5:26 ` Ian Rogers
2024-02-09 3:14 ` weilin.wang [this message]
2024-03-24 5:46 ` [RFC PATCH v4 13/15] perf stat: Code refactoring " Ian Rogers
2024-02-09 3:14 ` [RFC PATCH v4 14/15] perf stat: Add tool events support " weilin.wang
2024-03-24 5:56 ` Ian Rogers
2024-04-09 20:51 ` Wang, Weilin
2024-04-10 17:47 ` Ian Rogers
2024-02-09 3:14 ` [RFC PATCH v4 15/15] perf stat: Add hardware-grouping cmd option to perf stat weilin.wang
2024-03-24 5: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=20240209031441.943012-14-weilin.wang@intel.com \
--to=weilin.wang@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.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=namhyung@kernel.org \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=samantha.alt@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).