From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>, Andi Kleen <ak@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/10] perf scripting python: Improve general scripting for Intel PT
Date: Tue, 25 May 2021 09:58:53 -0300 [thread overview]
Message-ID: <YKz0jWpWHmNSr+bS@kernel.org> (raw)
In-Reply-To: <20210525095112.1399-1-adrian.hunter@intel.com>
Em Tue, May 25, 2021 at 12:51:02PM +0300, Adrian Hunter escreveu:
> Hi
>
> These patches make it easier to customize scripting for Intel PT traces.
>
> The first patch is a dependent fix.
>
> Subsequent patches add more information to python scripting.
>
> The final patch adds a branch trace to the intel-pt-events.py script
> which previously supported only power events and ptwrite.
Thanks, applied.
- Arnaldo
>
> Adrian Hunter (10):
> perf scripting python: Fix tuple_set_u64()
> perf scripting python: Factor out set_sym_in_dict()
> perf scripting python: Add 'addr_location' for 'addr'
> perf script: Factor out perf_sample__sprintf_flags()
> perf scripting python: Add sample flags
> perf scripting python: Add IPC
> perf scripting python: Add cpumode
> perf scripting python: Add context switch
> perf scripting python: Add auxtrace error
> perf scripts python: intel-pt-events.py: Add branches to script
>
> tools/perf/builtin-script.c | 56 +++-
> .../perf/scripts/python/bin/intel-pt-events-record | 4 +-
> .../perf/scripts/python/bin/intel-pt-events-report | 4 +-
> tools/perf/scripts/python/intel-pt-events.py | 143 +++++++--
> tools/perf/util/db-export.c | 12 +-
> tools/perf/util/db-export.h | 2 +-
> .../perf/util/scripting-engines/trace-event-perl.c | 3 +-
> .../util/scripting-engines/trace-event-python.c | 321 +++++++++++++++------
> tools/perf/util/trace-event-scripting.c | 3 +-
> tools/perf/util/trace-event.h | 8 +-
> 10 files changed, 415 insertions(+), 141 deletions(-)
>
>
> Regards
> Adrian
--
- Arnaldo
prev parent reply other threads:[~2021-05-25 12:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 9:51 [PATCH 00/10] perf scripting python: Improve general scripting for Intel PT Adrian Hunter
2021-05-25 9:51 ` [PATCH 01/10] perf scripting python: Fix tuple_set_u64() Adrian Hunter
2021-05-25 9:51 ` [PATCH 02/10] perf scripting python: Factor out set_sym_in_dict() Adrian Hunter
2021-05-25 9:51 ` [PATCH 03/10] perf scripting python: Add 'addr_location' for 'addr' Adrian Hunter
2021-05-25 9:51 ` [PATCH 04/10] perf script: Factor out perf_sample__sprintf_flags() Adrian Hunter
2021-05-25 9:51 ` [PATCH 05/10] perf scripting python: Add sample flags Adrian Hunter
2021-05-25 9:51 ` [PATCH 06/10] perf scripting python: Add IPC Adrian Hunter
2021-05-25 9:51 ` [PATCH 07/10] perf scripting python: Add cpumode Adrian Hunter
2021-05-25 9:51 ` [PATCH 08/10] perf scripting python: Add context switch Adrian Hunter
2021-05-25 9:51 ` [PATCH 09/10] perf scripting python: Add auxtrace error Adrian Hunter
2021-05-25 13:03 ` Arnaldo Carvalho de Melo
2021-05-25 18:30 ` Adrian Hunter
2021-05-25 19:54 ` Arnaldo Carvalho de Melo
2021-05-25 9:51 ` [PATCH 10/10] perf scripts python: intel-pt-events.py: Add branches to script Adrian Hunter
2021-05-25 12:58 ` Arnaldo Carvalho de Melo [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=YKz0jWpWHmNSr+bS@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.