All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
Cc: Ian Rogers <irogers@google.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	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>,
	James Clark <james.clark@linaro.org>,
	Dominique Martinet <asmadeus@codewreck.org>,
	Andi Kleen <ak@linux.intel.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	Thomas Falcon <thomas.falcon@intel.com>
Subject: Re: [PATCH v2 4/5] perf x86 evlist: Update comments on topdown regrouping
Date: Tue, 11 Mar 2025 19:00:33 -0700	[thread overview]
Message-ID: <Z9Dqwd_7pyj7Gvqj@google.com> (raw)
In-Reply-To: <ba8dedbc-9a5f-4038-ad51-2b20baa6af65@linux.intel.com>

On Tue, Mar 11, 2025 at 08:45:20AM +0800, Mi, Dapeng wrote:
> 
> On 3/11/2025 5:25 AM, Namhyung Kim wrote:
> > Hello,
> >
> > On Thu, Mar 06, 2025 at 06:39:05PM -0800, Ian Rogers wrote:
> >> From: Dapeng Mi <dapeng1.mi@linux.intel.com>
> >>
> >> Update to remove comments about groupings not working and with the:
> >> ```
> >> perf stat -e "{instructions,slots},{cycles,topdown-retiring}"
> >> ```
> >> case that now works.
> >>
> >> Signed-off-by: Ian Rogers <irogers@google.com>
> > Dapeng, can I get your Signed-off-by here?
> >
> > Thanks,
> > Namhyung
> >
> >> ---
> >>  tools/perf/arch/x86/util/evlist.c | 27 ++++++---------------------
> >>  1 file changed, 6 insertions(+), 21 deletions(-)
> >>
> >> diff --git a/tools/perf/arch/x86/util/evlist.c b/tools/perf/arch/x86/util/evlist.c
> >> index ed205d1b207d..7905a28d7734 100644
> >> --- a/tools/perf/arch/x86/util/evlist.c
> >> +++ b/tools/perf/arch/x86/util/evlist.c
> >> @@ -39,28 +39,13 @@ int arch_evlist__cmp(const struct evsel *lhs, const struct evsel *rhs)
> >>  	 *         26,319,024      slots
> >>  	 *          2,427,791      instructions
> >>  	 *          2,683,508      topdown-retiring
> >> -	 *
> >> -	 * If slots event and topdown metrics events are not in same group, the
> >> -	 * topdown metrics events must be first event after the slots event group,
> >> -	 * otherwise topdown metrics events can't be regrouped correctly, e.g.
> >> -	 *
> >> -	 * a. perf stat -e "{instructions,slots},cycles,topdown-retiring" -C0 sleep 1
> >> -	 *    WARNING: events were regrouped to match PMUs
> >> -	 *     Performance counter stats for 'CPU(s) 0':
> >> -	 *         17,923,134      slots
> >> -	 *          2,154,855      instructions
> >> -	 *          3,015,058      cycles
> >> -	 *    <not supported>      topdown-retiring
> >> -	 *
> >> -	 * If slots event and topdown metrics events are in two groups, the group which
> >> -	 * has topdown metrics events must contain only the topdown metrics event,
> >> -	 * otherwise topdown metrics event can't be regrouped correctly as well, e.g.
> >> -	 *
> >> -	 * a. perf stat -e "{instructions,slots},{topdown-retiring,cycles}" -C0 sleep 1
> >> +	 * e. slots event and metrics event are in a group and not adjacent
> 
> Yes, here is my SoB.
> 
> Signed-off-by: Dapeng Mi <dapeng1.mi@linux.intel.com>

Thanks!

> 
> BTW, It seems there is a typo and missed the "not" word. It should be 
> "slots event and metrics event are not in a group and not adjacent"
 
Ok, will update.

Thanks,
Namhyung

> 
> >> +	 *    perf stat -e "{instructions,slots},cycles,topdown-retiring" -C0 sleep 1
> >>  	 *    WARNING: events were regrouped to match PMUs
> >> -	 *    Error:
> >> -	 *    The sys_perf_event_open() syscall returned with 22 (Invalid argument) for
> >> -	 *    event (topdown-retiring)
> >> +	 *         68,433,522      slots
> >> +	 *          8,856,102      topdown-retiring
> >> +	 *          7,791,494      instructions
> >> +	 *         11,469,513      cycles
> >>  	 */
> >>  	if (topdown_sys_has_perf_metrics() &&
> >>  	    (arch_evsel__must_be_in_group(lhs) || arch_evsel__must_be_in_group(rhs))) {
> >> -- 
> >> 2.49.0.rc0.332.g42c0ae87b1-goog
> >>

  reply	other threads:[~2025-03-12  2:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07  2:39 [PATCH v2 1/5] perf tools: Improve handling of hybrid PMUs in perf_event_attr__fprintf Ian Rogers
2025-03-07  2:39 ` [PATCH v2 2/5] perf x86/topdown: Fix topdown leader sampling test error on hybrid Ian Rogers
2025-03-07  2:39 ` [PATCH v2 3/5] perf parse-events: Corrections to topdown sorting Ian Rogers
2025-03-07  9:52   ` Mi, Dapeng
2025-03-07  2:39 ` [PATCH v2 4/5] perf x86 evlist: Update comments on topdown regrouping Ian Rogers
2025-03-10 21:25   ` Namhyung Kim
2025-03-11  0:45     ` Mi, Dapeng
2025-03-12  2:00       ` Namhyung Kim [this message]
2025-03-07  2:39 ` [PATCH v2 5/5] perf test stat: Additional topdown grouping tests Ian Rogers
2025-03-12 19:53 ` [PATCH v2 1/5] perf tools: Improve handling of hybrid PMUs in perf_event_attr__fprintf Namhyung Kim

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=Z9Dqwd_7pyj7Gvqj@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=asmadeus@codewreck.org \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --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=thomas.falcon@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 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.