[PATCH] perf: Util.py add_stats() computes the mean correctly

2017-08-08 Thread Dima Kogan
add_stats() is a utility function for perf scripts to accumulate a value, and keep track of some statistics. The mean is one of the statistics it keeps track of, but due to a bug, this wasn't being computed properly. This patch makes the computation correct Signed-off-by: Dima Kogan &l

[PATCH] perf: Util.py add_stats() computes the mean correctly

2017-08-08 Thread Dima Kogan
add_stats() is a utility function for perf scripts to accumulate a value, and keep track of some statistics. The mean is one of the statistics it keeps track of, but due to a bug, this wasn't being computed properly. This patch makes the computation correct Signed-off-by: Dima Kogan --- tools

[tip:perf/core] perf script perl: Perl scripts now get a backtrace, like the python ones

2016-03-31 Thread tip-bot for Dima Kogan
Commit-ID: f7380c12ec6cfd69f274ba6181cd01c764f877bb Gitweb: http://git.kernel.org/tip/f7380c12ec6cfd69f274ba6181cd01c764f877bb Author: Dima Kogan <d...@secretsauce.net> AuthorDate: Tue, 29 Mar 2016 12:47:53 -0300 Committer: Arnaldo Carvalho de Melo <a...@redhat.com> CommitD

[tip:perf/core] perf script perl: Perl scripts now get a backtrace, like the python ones

2016-03-31 Thread tip-bot for Dima Kogan
Commit-ID: f7380c12ec6cfd69f274ba6181cd01c764f877bb Gitweb: http://git.kernel.org/tip/f7380c12ec6cfd69f274ba6181cd01c764f877bb Author: Dima Kogan AuthorDate: Tue, 29 Mar 2016 12:47:53 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 30 Mar 2016 11:14:09 -0300 perf script

Re: [PATCH] perf: perl scripts now get a backtrace, like the python scripts

2016-03-29 Thread Dima Kogan
Arnaldo Carvalho de Melo <a...@kernel.org> writes: > Em Fri, Mar 25, 2016 at 11:31:54AM -0700, Dima Kogan escreveu: >> Hi. >> >> Currently the python perf scripts get a backtrace, while the perl ones do >> not. >> This patch adds that to the perl script

Re: [PATCH] perf: perl scripts now get a backtrace, like the python scripts

2016-03-29 Thread Dima Kogan
Arnaldo Carvalho de Melo writes: > Em Fri, Mar 25, 2016 at 11:31:54AM -0700, Dima Kogan escreveu: >> Hi. >> >> Currently the python perf scripts get a backtrace, while the perl ones do >> not. >> This patch adds that to the perl scripts as well. > > Can

[PATCH] perf: perl scripts now get a backtrace, like the python scripts

2016-03-25 Thread Dima Kogan
Hi. Currently the python perf scripts get a backtrace, while the perl ones do not. This patch adds that to the perl scripts as well. --- .../perf/util/scripting-engines/trace-event-perl.c | 115 +++-- 1 file changed, 107 insertions(+), 8 deletions(-) diff --git

[PATCH] perf: perl scripts now get a backtrace, like the python scripts

2016-03-25 Thread Dima Kogan
Hi. Currently the python perf scripts get a backtrace, while the perl ones do not. This patch adds that to the perl scripts as well. --- .../perf/util/scripting-engines/trace-event-perl.c | 115 +++-- 1 file changed, 107 insertions(+), 8 deletions(-) diff --git

Perf misreports userspace args to unoptimized functions

2016-03-24 Thread Dima Kogan
Hi. I'm seeing an issue with the way perf interfaces with uprobes that results in incorrect printing of function arguments under fairly normal conditions. Example: Let's say I have a trivial C program tst.c: = #include #include int f(int x) { return

Perf misreports userspace args to unoptimized functions

2016-03-24 Thread Dima Kogan
Hi. I'm seeing an issue with the way perf interfaces with uprobes that results in incorrect printing of function arguments under fairly normal conditions. Example: Let's say I have a trivial C program tst.c: = #include #include int f(int x) { return

[tip:perf/core] perf symbols: Fix type error when reading a build-id

2015-10-29 Thread tip-bot for Dima Kogan
Commit-ID: f2f3096888569ff1fc15fa0187a39eef3a24b28e Gitweb: http://git.kernel.org/tip/f2f3096888569ff1fc15fa0187a39eef3a24b28e Author: Dima Kogan AuthorDate: Mon, 7 Sep 2015 17:30:28 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 28 Oct 2015 10:02:00 -0300 perf symbols

[tip:perf/core] perf symbols: we can now read separate debug-info files based on a build ID

2015-10-29 Thread tip-bot for Dima Kogan
Commit-ID: 5baecbcd9c9a2f491afe1369fc22e7363f9c94d5 Gitweb: http://git.kernel.org/tip/5baecbcd9c9a2f491afe1369fc22e7363f9c94d5 Author: Dima Kogan AuthorDate: Mon, 7 Sep 2015 17:34:19 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 28 Oct 2015 10:04:27 -0300 perf symbols: we

[tip:perf/core] perf symbols: Fix type error when reading a build-id

2015-10-29 Thread tip-bot for Dima Kogan
Commit-ID: f2f3096888569ff1fc15fa0187a39eef3a24b28e Gitweb: http://git.kernel.org/tip/f2f3096888569ff1fc15fa0187a39eef3a24b28e Author: Dima Kogan <d...@secretsauce.net> AuthorDate: Mon, 7 Sep 2015 17:30:28 -0700 Committer: Arnaldo Carvalho de Melo <a...@redhat.com> CommitD

[tip:perf/core] perf symbols: we can now read separate debug-info files based on a build ID

2015-10-29 Thread tip-bot for Dima Kogan
Commit-ID: 5baecbcd9c9a2f491afe1369fc22e7363f9c94d5 Gitweb: http://git.kernel.org/tip/5baecbcd9c9a2f491afe1369fc22e7363f9c94d5 Author: Dima Kogan <d...@secretsauce.net> AuthorDate: Mon, 7 Sep 2015 17:34:19 -0700 Committer: Arnaldo Carvalho de Melo <a...@redhat.com> CommitD

Re: [PATCH 0/2] perf: we can now read separate debug-info files based on a build ID

2015-10-27 Thread Dima Kogan
Hi. I'd like to get this merged before I forget about it and then I hit this bug again at some point in the future. Any comment would be great. Thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo

Re: [PATCH 0/2] perf: we can now read separate debug-info files based on a build ID

2015-10-27 Thread Dima Kogan
Hi. I'd like to get this merged before I forget about it and then I hit this bug again at some point in the future. Any comment would be great. Thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo

Re: [PATCH 0/2] perf: we can now read separate debug-info files based on a build ID

2015-09-16 Thread Dima Kogan
Hi. This is a gentle ping. This patch fixes a real bug, and it'd be great if it was merged. Here's a demo. This is on a recent Debian/sid box, tracing malloc() calls in emacs. The debug symbols for libc and emacs are split into separate (installed) packages, as is the norm. $ perf probe -x

Re: [PATCH 0/2] perf: we can now read separate debug-info files based on a build ID

2015-09-16 Thread Dima Kogan
Hi. This is a gentle ping. This patch fixes a real bug, and it'd be great if it was merged. Here's a demo. This is on a recent Debian/sid box, tracing malloc() calls in emacs. The debug symbols for libc and emacs are split into separate (installed) packages, as is the norm. $ perf probe -x

[PATCH 0/2] perf: we can now read separate debug-info files based on a build ID

2015-09-07 Thread Dima Kogan
34.debug This patch series makes this work. The remaining two paths are still unchecked, but I don't know if they're "standard" anywhere Dima Kogan (2): perf: fixed type error when reading a build-id perf: we can now read separate debug-info files based on a build ID tools/

[PATCH 0/2] perf: we can now read separate debug-info files based on a build ID

2015-09-07 Thread Dima Kogan
34.debug This patch series makes this work. The remaining two paths are still unchecked, but I don't know if they're "standard" anywhere Dima Kogan (2): perf: fixed type error when reading a build-id perf: we can now read separate debug-info files based on a build ID tools/