public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Melo <arnaldo.melo@gmail.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Breno Leitao <leitao@debian.org>, Leo Yan <leo.yan@arm.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>,
	James Clark <james.clark@linaro.org>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@meta.com, Denis Yaroshevskiy <dyaroshev@meta.com>,
	Dmitry Ilvokhin <d@ilvokhin.com>
Subject: Re: [PATCH v2] perf stat: Fix crash on arm64
Date: Wed, 1 Apr 2026 17:56:26 -0300	[thread overview]
Message-ID: <ac2F5F1qShC9n2kE@x1> (raw)
In-Reply-To: <CAP-5=fUr4RdrGnnDE96GTQnpfj9anHVMxZ+gy7SwMEXGgm70uA@mail.gmail.com>

On Wed, Apr 01, 2026 at 01:16:49PM -0700, Ian Rogers wrote:
> On Fri, Mar 27, 2026 at 6:48 AM Arnaldo Melo <arnaldo.melo@gmail.com> wrote:
> >
> >
> >
> > On March 27, 2026 7:35:19 AM GMT-03:00, Breno Leitao <leitao@debian.org> wrote:
> > >On Thu, Mar 26, 2026 at 04:39:26PM +0000, Leo Yan wrote:
> > >> On Wed, Mar 25, 2026 at 03:27:05PM -0700, Ian Rogers wrote:
> > >>
> > >> > From the stack trace I don't see anything that should allow this.
> > >> > Either the list of metrics is broken, or the struct metric_event's
> > >> > evsel is NULL. But that should never happen as we wouldn't have a
> > >> > metric at that point. The sorting shouldn't affect that. If you can
> > >> > reproduce the issue, verbose logs may help.
> > >>
> > >> I believe I encountered a different issue, which is irrelevant to this
> > >> patch.  So Breno's patch is fine for me.
>
> > >That said, are there any concerns about merging this patch in its
> > >current form?

> > I guess not, will try and merge it later today for 7
> > 0.

> Looks like this one is still missing. Thanks,

So I think its too late for 7.0, I guess Namhyung should get it for
perf-tools-next, the fixes tag will make it get into the upcoming stable
series.

- Arnaldo

  reply	other threads:[~2026-04-01 20:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 10:24 [PATCH v2] perf stat: Fix crash on arm64 Breno Leitao
2026-03-25 18:25 ` Ian Rogers
2026-03-25 20:59 ` Leo Yan
2026-03-25 22:27   ` Ian Rogers
2026-03-26 16:39     ` Leo Yan
2026-03-26 21:21       ` Ian Rogers
2026-03-27 17:57         ` Leo Yan
2026-03-27 10:35       ` Breno Leitao
2026-03-27 13:48         ` Arnaldo Melo
2026-04-01 20:16           ` Ian Rogers
2026-04-01 20:56             ` Arnaldo Carvalho de Melo [this message]
2026-04-02 21:57 ` 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=ac2F5F1qShC9n2kE@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=d@ilvokhin.com \
    --cc=dyaroshev@meta.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=leitao@debian.org \
    --cc=leo.yan@arm.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=peterz@infradead.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