public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH v2] perf tools: Ensure event leader stays at head of evlist after sorting
@ 2026-05-01 22:33 Chun-Tse Shao
  2026-05-04  1:50 ` Namhyung Kim
  0 siblings, 1 reply; 3+ messages in thread
From: Chun-Tse Shao @ 2026-05-01 22:33 UTC (permalink / raw)
  To: linux-kernel
  Cc: Ian Rogers, Chun-Tse Shao, peterz, mingo, acme, namhyung,
	mark.rutland, alexander.shishkin, jolsa, adrian.hunter,
	james.clark, thomas.falcon, tmricht, linux-perf-users

From: Ian Rogers <irogers@google.com>

For evlist of a certain event/metric, the HEAD should be the event
leader. In some scenarios where uncore_xxx_0 does not exist, the event
leader is not the first element after sorting. For example, on my test
machine uncore_iio_0 does not exist, the event leader is uncore_iio_2.

However, in `evlist__cmp`, it was reordered based on the PMU name, which
makes uncore_iio_1 the HEAD of evlist, breaking the following merge
logic in `evsel__merge_aliases`.

The patch adds a loop at the end of
`parse_events__sort_events_and_fix_groups` to make sure the first
wildcard match is the earliest entry in the list, updating pointers
accordingly without breaking reordering detection.

Tested on device lacks uncore_iio_0, and `perf test` looks good.

Signed-off-by: Ian Rogers <irogers@google.com>
Signed-off-by: Chun-Tse Shao <ctshao@google.com>
---
v2:
  Adding missing Signed-off-by from Ian Rogers.
  Renaming variable `l` to `orig_leader`.

v1: lore.kernel.org/20260501043532.790711-1-ctshao@google.com

 tools/perf/util/parse-events.c | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/tools/perf/util/parse-events.c b/tools/perf/util/parse-events.c
index 1497e1f2a08c..be825617321d 100644
--- a/tools/perf/util/parse-events.c
+++ b/tools/perf/util/parse-events.c
@@ -2251,6 +2251,33 @@ static int parse_events__sort_events_and_fix_groups(struct list_head *list)
 		}
 		last_event_was_forced_leader = (force_grouped_leader == pos);
 	}
+
+	/*
+	 * Make sure the first wildcard match is the earliest entry in the list.
+	 * Since list_sort might have reordered the aliases, the original leader
+	 * might not be at the head of the list anymore. We find the first
+	 * alias in the sorted list and make it the new leader, and redirect
+	 * all other aliases to it.
+	 */
+	list_for_each_entry(pos, list, core.node) {
+		struct evsel *l = pos->first_wildcard_match;
+
+		if (!l)
+			continue;
+
+		if (l->first_wildcard_match) {
+			/* Original leader was redirected to a new leader */
+			pos->first_wildcard_match = l->first_wildcard_match;
+		} else if (pos->core.idx < l->core.idx) {
+			/*
+			 * We are earlier than the original leader in sorted order,
+			 * and no earlier alias has claimed leadership yet.
+			 */
+			l->first_wildcard_match = pos;
+			pos->first_wildcard_match = NULL;
+		}
+	}
+
 	list_for_each_entry(pos, list, core.node) {
 		struct evsel *pos_leader = evsel__leader(pos);

--
2.54.0.545.g6539524ca2-goog


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH v2] perf tools: Ensure event leader stays at head of evlist after sorting
  2026-05-01 22:33 [PATCH v2] perf tools: Ensure event leader stays at head of evlist after sorting Chun-Tse Shao
@ 2026-05-04  1:50 ` Namhyung Kim
  2026-05-05 21:22   ` Chun-Tse Shao
  0 siblings, 1 reply; 3+ messages in thread
From: Namhyung Kim @ 2026-05-04  1:50 UTC (permalink / raw)
  To: Chun-Tse Shao
  Cc: linux-kernel, Ian Rogers, peterz, mingo, acme, mark.rutland,
	alexander.shishkin, jolsa, adrian.hunter, james.clark,
	thomas.falcon, tmricht, linux-perf-users

On Fri, May 01, 2026 at 03:33:47PM -0700, Chun-Tse Shao wrote:
> From: Ian Rogers <irogers@google.com>
> 
> For evlist of a certain event/metric, the HEAD should be the event
> leader. In some scenarios where uncore_xxx_0 does not exist, the event
> leader is not the first element after sorting. For example, on my test
> machine uncore_iio_0 does not exist, the event leader is uncore_iio_2.
> 
> However, in `evlist__cmp`, it was reordered based on the PMU name, which
> makes uncore_iio_1 the HEAD of evlist, breaking the following merge
> logic in `evsel__merge_aliases`.
> 
> The patch adds a loop at the end of
> `parse_events__sort_events_and_fix_groups` to make sure the first
> wildcard match is the earliest entry in the list, updating pointers
> accordingly without breaking reordering detection.
> 
> Tested on device lacks uncore_iio_0, and `perf test` looks good.
> 
> Signed-off-by: Ian Rogers <irogers@google.com>
> Signed-off-by: Chun-Tse Shao <ctshao@google.com>
> ---
> v2:
>   Adding missing Signed-off-by from Ian Rogers.
>   Renaming variable `l` to `orig_leader`.

I can't see this.

Thanks,
Namhyung

> 
> v1: lore.kernel.org/20260501043532.790711-1-ctshao@google.com
> 
>  tools/perf/util/parse-events.c | 27 +++++++++++++++++++++++++++
>  1 file changed, 27 insertions(+)
> 
> diff --git a/tools/perf/util/parse-events.c b/tools/perf/util/parse-events.c
> index 1497e1f2a08c..be825617321d 100644
> --- a/tools/perf/util/parse-events.c
> +++ b/tools/perf/util/parse-events.c
> @@ -2251,6 +2251,33 @@ static int parse_events__sort_events_and_fix_groups(struct list_head *list)
>  		}
>  		last_event_was_forced_leader = (force_grouped_leader == pos);
>  	}
> +
> +	/*
> +	 * Make sure the first wildcard match is the earliest entry in the list.
> +	 * Since list_sort might have reordered the aliases, the original leader
> +	 * might not be at the head of the list anymore. We find the first
> +	 * alias in the sorted list and make it the new leader, and redirect
> +	 * all other aliases to it.
> +	 */
> +	list_for_each_entry(pos, list, core.node) {
> +		struct evsel *l = pos->first_wildcard_match;
> +
> +		if (!l)
> +			continue;
> +
> +		if (l->first_wildcard_match) {
> +			/* Original leader was redirected to a new leader */
> +			pos->first_wildcard_match = l->first_wildcard_match;
> +		} else if (pos->core.idx < l->core.idx) {
> +			/*
> +			 * We are earlier than the original leader in sorted order,
> +			 * and no earlier alias has claimed leadership yet.
> +			 */
> +			l->first_wildcard_match = pos;
> +			pos->first_wildcard_match = NULL;
> +		}
> +	}
> +
>  	list_for_each_entry(pos, list, core.node) {
>  		struct evsel *pos_leader = evsel__leader(pos);
> 
> --
> 2.54.0.545.g6539524ca2-goog
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH v2] perf tools: Ensure event leader stays at head of evlist after sorting
  2026-05-04  1:50 ` Namhyung Kim
@ 2026-05-05 21:22   ` Chun-Tse Shao
  0 siblings, 0 replies; 3+ messages in thread
From: Chun-Tse Shao @ 2026-05-05 21:22 UTC (permalink / raw)
  To: Namhyung Kim
  Cc: linux-kernel, Ian Rogers, peterz, mingo, acme, mark.rutland,
	alexander.shishkin, jolsa, adrian.hunter, james.clark,
	thomas.falcon, tmricht, linux-perf-users

My apologies, resend the patch:
lore.kernel.org/20260505211924.1961056-2-ctshao@google.com

On Sun, May 3, 2026 at 6:51 PM Namhyung Kim <namhyung@kernel.org> wrote:
>
> On Fri, May 01, 2026 at 03:33:47PM -0700, Chun-Tse Shao wrote:
> > From: Ian Rogers <irogers@google.com>
> >
> > For evlist of a certain event/metric, the HEAD should be the event
> > leader. In some scenarios where uncore_xxx_0 does not exist, the event
> > leader is not the first element after sorting. For example, on my test
> > machine uncore_iio_0 does not exist, the event leader is uncore_iio_2.
> >
> > However, in `evlist__cmp`, it was reordered based on the PMU name, which
> > makes uncore_iio_1 the HEAD of evlist, breaking the following merge
> > logic in `evsel__merge_aliases`.
> >
> > The patch adds a loop at the end of
> > `parse_events__sort_events_and_fix_groups` to make sure the first
> > wildcard match is the earliest entry in the list, updating pointers
> > accordingly without breaking reordering detection.
> >
> > Tested on device lacks uncore_iio_0, and `perf test` looks good.
> >
> > Signed-off-by: Ian Rogers <irogers@google.com>
> > Signed-off-by: Chun-Tse Shao <ctshao@google.com>
> > ---
> > v2:
> >   Adding missing Signed-off-by from Ian Rogers.
> >   Renaming variable `l` to `orig_leader`.
>
> I can't see this.
>
> Thanks,
> Namhyung
>
> >
> > v1: lore.kernel.org/20260501043532.790711-1-ctshao@google.com
> >
> >  tools/perf/util/parse-events.c | 27 +++++++++++++++++++++++++++
> >  1 file changed, 27 insertions(+)
> >
> > diff --git a/tools/perf/util/parse-events.c b/tools/perf/util/parse-events.c
> > index 1497e1f2a08c..be825617321d 100644
> > --- a/tools/perf/util/parse-events.c
> > +++ b/tools/perf/util/parse-events.c
> > @@ -2251,6 +2251,33 @@ static int parse_events__sort_events_and_fix_groups(struct list_head *list)
> >               }
> >               last_event_was_forced_leader = (force_grouped_leader == pos);
> >       }
> > +
> > +     /*
> > +      * Make sure the first wildcard match is the earliest entry in the list.
> > +      * Since list_sort might have reordered the aliases, the original leader
> > +      * might not be at the head of the list anymore. We find the first
> > +      * alias in the sorted list and make it the new leader, and redirect
> > +      * all other aliases to it.
> > +      */
> > +     list_for_each_entry(pos, list, core.node) {
> > +             struct evsel *l = pos->first_wildcard_match;
> > +
> > +             if (!l)
> > +                     continue;
> > +
> > +             if (l->first_wildcard_match) {
> > +                     /* Original leader was redirected to a new leader */
> > +                     pos->first_wildcard_match = l->first_wildcard_match;
> > +             } else if (pos->core.idx < l->core.idx) {
> > +                     /*
> > +                      * We are earlier than the original leader in sorted order,
> > +                      * and no earlier alias has claimed leadership yet.
> > +                      */
> > +                     l->first_wildcard_match = pos;
> > +                     pos->first_wildcard_match = NULL;
> > +             }
> > +     }
> > +
> >       list_for_each_entry(pos, list, core.node) {
> >               struct evsel *pos_leader = evsel__leader(pos);
> >
> > --
> > 2.54.0.545.g6539524ca2-goog
> >

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-05-05 21:22 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-01 22:33 [PATCH v2] perf tools: Ensure event leader stays at head of evlist after sorting Chun-Tse Shao
2026-05-04  1:50 ` Namhyung Kim
2026-05-05 21:22   ` Chun-Tse Shao

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox