From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@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>,
Michael Petlan <mpetlan@redhat.com>,
Andi Kleen <ak@linux.intel.com>,
Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/4] perf evsel: Missed close when probing hybrid core PMUs
Date: Mon, 16 Jun 2025 13:24:24 -0300 [thread overview]
Message-ID: <aFBFOBUhHnF87R9q@x1> (raw)
In-Reply-To: <CAP-5=fUz6ViPHDdS9GCAEYUN39L4MpAnRR4CzJWggg0S8vn39A@mail.gmail.com>
On Mon, Jun 16, 2025 at 09:04:41AM -0700, Ian Rogers wrote:
> On Fri, Jun 13, 2025 at 5:41 PM Ian Rogers <irogers@google.com> wrote:
> > Add missing close to avoid leaking perf events. In past perfs this
> > mattered little as the function was just used by perf list. As the
> > function is now used to detect hybrid PMUs leaking the perf event is
> > somewhat more painful.
> Given this leads to leaking perf events on hybrid systems it would be
> nice to land this 1 liner in the next v6.15 rc pull request fixes if
> possible.
Sure.
Just one nit: while looking at:
void evsel__close(struct evsel *evsel)
{
if (evsel__is_retire_lat(evsel))
evsel__tpebs_close(evsel);
perf_evsel__close(&evsel->core);
perf_evsel__free_id(&evsel->core);
}
And then:
void evsel__delete(struct evsel *evsel)
{
if (!evsel)
return;
evsel__exit(evsel);
free(evsel);
}
and:
void evsel__exit(struct evsel *evsel)
{
assert(list_empty(&evsel->core.node));
assert(evsel->evlist == NULL);
if (evsel__is_retire_lat(evsel))
evsel__tpebs_close(evsel);
<SNIP>
I think that tpebs_close could be done just at evsel__close(), no?
The way it works I think there is no problem with calling it now twice,
but it fits better in evsel__close().
- Arnaldo
next prev parent reply other threads:[~2025-06-16 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 0:41 [PATCH v1 1/4] perf test: Directory file descriptor leak Ian Rogers
2025-06-14 0:41 ` [PATCH v1 2/4] perf evsel: Missed close when probing hybrid core PMUs Ian Rogers
2025-06-16 16:04 ` Ian Rogers
2025-06-16 16:24 ` Arnaldo Carvalho de Melo [this message]
2025-06-16 16:30 ` Ian Rogers
2025-06-14 0:41 ` [PATCH v1 3/4] perf trace: Add missed freeing of ordered events and thread Ian Rogers
2025-06-14 4:16 ` Howard Chu
2025-06-16 16:27 ` Arnaldo Carvalho de Melo
2025-06-17 21:30 ` Arnaldo Carvalho de Melo
2025-06-17 21:32 ` Ian Rogers
2025-06-17 21:49 ` Arnaldo Carvalho de Melo
2025-06-23 22:26 ` Ian Rogers
2025-06-14 0:41 ` [PATCH v1 4/4] libperf evsel: In exit add missed puts and assert close, etc. were called 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=aFBFOBUhHnF87R9q@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jiapeng.chong@linux.alibaba.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=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yangtiezhu@loongson.cn \
/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).