From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: "Liang, Kan" <kan.liang@linux.intel.com>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <ak@linux.intel.com>,
"Yasin, Ahmad" <ahmad.yasin@intel.com>,
"Taylor, Perry" <perry.taylor@intel.com>,
"Alt, Samantha" <samantha.alt@intel.com>,
"Biggers, Caleb" <caleb.biggers@intel.com>,
"Wang, Weilin" <weilin.wang@intel.com>,
Edward <edward.baker@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>, Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Florian Fischer <florian.fischer@muhq.space>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] perf stat: Introduce skippable evsels
Date: Thu, 20 Apr 2023 08:33:57 -0300 [thread overview]
Message-ID: <ZEEjJVTIcXvsV4Fh@kernel.org> (raw)
In-Reply-To: <CAP-5=fVWN5=URg0Og7KW7f7L4LSw6D8ghOKjP7La=0c+MkXFCg@mail.gmail.com>
Em Wed, Apr 19, 2023 at 09:51:20AM -0700, Ian Rogers escreveu:
> On Wed, Apr 19, 2023 at 7:16 AM Liang, Kan <kan.liang@linux.intel.com> wrote:
> > For ADL/RPL platforms
> > - Segmentation fault which I just found this morning.
> > # ./perf stat true
> > Segmentation fault (core dumped)
> This may also stem from the reference count checking work that Arnaldo
> is currently merging. It is hard to test hybrid because it uses
> non-generic code paths.
Hey, could you please try this under gdb and provide a backtrace? It may
indeed be related to this refcount checking work, there was a bug fixed
by the ARM guys for cs-etm and I combed thru and fixed some other use
before check for NULL cases, maybe one more slipped up.
Here I couldn't reproduce, but I don't have a Intel hybrid system, will
check with an ARM, but unsure if it will exercise the same code paths...
- Arnaldo
next prev parent reply other threads:[~2023-04-20 11:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 5:19 [PATCH v2] perf stat: Introduce skippable evsels Ian Rogers
2023-04-14 18:02 ` Liang, Kan
2023-04-14 23:03 ` Ian Rogers
2023-04-17 13:58 ` Liang, Kan
2023-04-17 15:59 ` Ian Rogers
2023-04-17 17:31 ` Liang, Kan
2023-04-17 18:13 ` Ian Rogers
2023-04-18 13:03 ` Liang, Kan
2023-04-18 15:43 ` Ian Rogers
2023-04-18 18:19 ` Liang, Kan
2023-04-18 20:08 ` Ian Rogers
2023-04-18 21:51 ` Liang, Kan
2023-04-19 0:12 ` Ian Rogers
2023-04-19 1:00 ` Ian Rogers
2023-04-19 12:31 ` Liang, Kan
2023-04-19 13:19 ` Ian Rogers
2023-04-19 14:16 ` Liang, Kan
2023-04-19 16:51 ` Ian Rogers
2023-04-19 18:57 ` Liang, Kan
2023-04-20 0:23 ` Ian Rogers
2023-04-20 13:02 ` Liang, Kan
2023-04-21 0:19 ` Ian Rogers
2023-04-21 13:32 ` Liang, Kan
2023-04-21 15:49 ` Ian Rogers
2023-04-21 17:10 ` Liang, Kan
2023-04-21 17:30 ` Ian Rogers
2023-04-21 15:58 ` Ian Rogers
2023-04-20 11:33 ` Arnaldo Carvalho de Melo [this message]
2023-04-20 12:22 ` Liang, Kan
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=ZEEjJVTIcXvsV4Fh@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ahmad.yasin@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=edward.baker@intel.com \
--cc=eranian@google.com \
--cc=florian.fischer@muhq.space \
--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 \
--cc=weilin.wang@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).