From: Chris Phlipot <cphlipot0@gmail.com>
To: adrian.hunter@intel.com, acme@kernel.org, peterz@infradead.org,
mingo@redhat.com
Cc: linux-kernel@vger.kernel.org, Chris Phlipot <cphlipot0@gmail.com>
Subject: [PATCH 0/4] perf script: fix duplicate symbols in db-export
Date: Tue, 10 May 2016 19:04:01 -0700 [thread overview]
Message-ID: <1462932245-4656-1-git-send-email-cphlipot0@gmail.com> (raw)
This patch set contains 3 fixes for duplicate symbol creation in the
db-export implementation and one new symbol API required for the fixes.
commit 9c7b37cd63d0 already removed the majority of duplicates, but these
fixes take care of the remaining corner cases.
each patch (except for the 1st, which is a dependency for patch 2) reduces
the number of duplicate symbols exported. When all patches are applied,
my test workload has no more duplicate symbols being exported.
Tests ran:
$perf record --call-graph=dwarf stress -c 2 -t 20
$perf script -s scripts/python/export-to-postgresql.py test all callchains
$psql test
To show the effect of the changes we run the following query before/after
the changes on a database created using the export-to-postgresql.py script
with callchains enabled. If this query returns any value greater than 1,
then it means that there are duplicates present.
In the test workload, at least one symbol occurs 299 times before applying
the fixes:
test=# select count(*) as cnt from symbols group by
sym_start,sym_end,dso_id order by cnt desc limit 1;
cnt
-----
299
(1 row)
After applying the fixes no symbol occurs more than once:
test=# select count(*) as cnt from symbols group by
sym_start,sym_end,dso_id order by cnt desc limit 1;
cnt
-----
1
(1 row)
Chris Phlipot (4):
perf symbols: add dso__insert_symbol function
perf script: fix symbol insertion behavior in db-export
perf script: fix callchain addresses in db-export
perf script: fix export of callchains with recursion in db-export
tools/perf/util/db-export.c | 12 ++++++------
tools/perf/util/symbol.c | 12 ++++++++++++
tools/perf/util/symbol.h | 3 +++
3 files changed, 21 insertions(+), 6 deletions(-)
--
2.7.4
next reply other threads:[~2016-05-11 2:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 2:04 Chris Phlipot [this message]
2016-05-11 2:04 ` [PATCH 1/4] perf symbols: add dso__insert_symbol function Chris Phlipot
2016-05-11 2:04 ` [PATCH 2/4] perf script: fix symbol insertion behavior in db-export Chris Phlipot
2016-05-11 2:04 ` [PATCH 3/4] perf script: fix callchain addresses " Chris Phlipot
2016-05-11 2:04 ` [PATCH 4/4] perf script: fix export of callchains with recursion " Chris Phlipot
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=1462932245-4656-1-git-send-email-cphlipot0@gmail.com \
--to=cphlipot0@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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