From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>, Ian Rogers <irogers@google.com>
Subject: Re: [PATCHSET 0/9] perf tools: Fix various memory leaks
Date: Mon, 7 Sep 2020 13:35:08 +0200 [thread overview]
Message-ID: <20200907113508.GL1199773@krava> (raw)
In-Reply-To: <20200907034502.753230-1-namhyung@kernel.org>
On Mon, Sep 07, 2020 at 12:44:53PM +0900, Namhyung Kim wrote:
> Hello,
>
> I've found and fixed a bunch of memory leaks during perf pmu and
> metric tests with address sanitizer. Before this, the tests were
> mostly failed due to the leaks since ASAN makes it return non-zero.
>
> Now I'm seeing no error with ASAN like below:
>
> $ ./perf test pmu metric
> 9: Parse perf pmu format : Ok
> 10: PMU events :
> 10.1: PMU event table sanity : Ok
> 10.2: PMU event map aliases : Ok
> 10.3: Parsing of PMU event table metrics : Skip (some metrics failed)
> 10.4: Parsing of PMU event table metrics with fake PMUs : Ok
> 67: Parse and process metrics : Ok
>
> The failure in 10.3 seems due to parse errors like below:
>
> Multiple errors dropping message: unknown term 'filter_opc' for pmu 'uncore_cbox_0'
> (valid terms: event,edge,inv,umask,cmask,config,config1,config2,name,period,freq,
> branch_type,time,call-graph,stack-size,no-inherit,inherit,max-stack,
> nr,no-overwrite,overwrite,driver-config,percore,aux-output,aux-sample-size)
>
>
> Parse event failed metric 'DRAM_Parallel_Reads' id 'arb/event=0x80,umask=0x2,thresh=1/'
> expr 'arb@event\=0x80\,umask\=0x2@ / arb@event\=0x80\,umask\=0x2\,thresh\=1@'
> Error string 'unknown term 'thresh' for pmu 'uncore_arb'' help
> 'valid terms: event,edge,inv,umask,cmask,config,config1,config2,name,period,freq,
> branch_type,time,call-graph,stack-size,no-inherit,inherit,max-stack,
> nr,no-overwrite,overwrite,driver-config,percore,aux-output,aux-sample-size'
>
>
> The patches are also available at 'perf/metric-fix-v1' branch on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
>
> Thanks
> Namhyung
>
>
> Namhyung Kim (9):
> perf evlist: Fix cpu/thread map leak
> perf parse-event: Fix cpu map leaks
> perf parse-event: Fix memory leak in evsel->unit
> perf test: Fix memory leaks in parse-metric test
> perf metric: Release expr_parse_ctx after testing
> perf metric: Free metric when it failed to resolve
> perf metric: Do not free metric when failed to resolve
> perf test: Free aliases for PMU event map aliases test
> perf test: Free formats for perf pmu parse test
Acked-by: Jiri Olsa <jolsa@redhat.com>
thanks,
jirka
prev parent reply other threads:[~2020-09-07 11:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 3:44 [PATCHSET 0/9] perf tools: Fix various memory leaks Namhyung Kim
2020-09-07 3:44 ` [PATCH 1/9] perf evlist: Fix cpu/thread map leak Namhyung Kim
2020-09-07 11:29 ` Jiri Olsa
2020-09-07 11:32 ` Jiri Olsa
2020-09-07 13:22 ` Namhyung Kim
2020-09-07 3:44 ` [PATCH 2/9] perf parse-event: Fix cpu map leaks Namhyung Kim
2020-09-07 3:44 ` [PATCH 3/9] perf parse-event: Fix memory leak in evsel->unit Namhyung Kim
2020-09-07 3:44 ` [PATCH 4/9] perf test: Fix memory leaks in parse-metric test Namhyung Kim
2020-09-07 3:44 ` [PATCH 5/9] perf metric: Release expr_parse_ctx after testing Namhyung Kim
2020-09-07 3:44 ` [PATCH 6/9] perf metric: Free metric when it failed to resolve Namhyung Kim
2020-09-07 3:45 ` [PATCH 7/9] perf metric: Do not free metric when " Namhyung Kim
2020-09-07 3:45 ` [PATCH 8/9] perf test: Free aliases for PMU event map aliases test Namhyung Kim
2020-09-07 10:28 ` John Garry
2020-09-07 13:20 ` Namhyung Kim
2020-09-07 13:47 ` John Garry
2020-09-07 3:45 ` [PATCH 9/9] perf test: Free formats for perf pmu parse test Namhyung Kim
2020-09-07 11:35 ` Jiri Olsa [this message]
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=20200907113508.GL1199773@krava \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.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;
as well as URLs for NNTP newsgroup(s).