From: Jiri Olsa <olsajiri@gmail.com>
To: Eelco Chaudron <echaudro@redhat.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf scripting python: expose symbol offset and source information
Date: Thu, 10 Feb 2022 08:52:20 +0100 [thread overview]
Message-ID: <YgTENKDfI/2+DZhJ@krava> (raw)
In-Reply-To: <164389947295.382219.17025049915445689710.stgit@wsfd-netdev64.ntdv.lab.eng.bos.redhat.com>
On Thu, Feb 03, 2022 at 09:44:33AM -0500, Eelco Chaudron wrote:
> This change adds the symbol offset to the data exported for each
> call-chain entry. This can not be calculated from the script and
> only the ip value, and no related mmap information.
>
> In addition, also export the source file and line information, if
> available, to avoid an external lookup if this information is needed.
could you please update Documentation/perf-script-python.txt with that?
any example script under scripts/python would be great
thanks,
jirka
>
> Signed-off-by: Eelco Chaudron <echaudro@redhat.com>
> ---
> .../util/scripting-engines/trace-event-python.c | 42 ++++++++++++++------
> 1 file changed, 30 insertions(+), 12 deletions(-)
>
> diff --git a/tools/perf/util/scripting-engines/trace-event-python.c b/tools/perf/util/scripting-engines/trace-event-python.c
> index e752e1f4a5f0..0f392b4ff663 100644
> --- a/tools/perf/util/scripting-engines/trace-event-python.c
> +++ b/tools/perf/util/scripting-engines/trace-event-python.c
> @@ -392,6 +392,18 @@ static const char *get_dsoname(struct map *map)
> return dsoname;
> }
>
> +static unsigned long get_offset(struct symbol *sym, struct addr_location *al)
> +{
> + unsigned long offset;
> +
> + if (al->addr < sym->end)
> + offset = al->addr - sym->start;
> + else
> + offset = al->addr - al->map->start - sym->start;
> +
> + return offset;
> +}
> +
> static PyObject *python_process_callchain(struct perf_sample *sample,
> struct evsel *evsel,
> struct addr_location *al)
> @@ -443,6 +455,24 @@ static PyObject *python_process_callchain(struct perf_sample *sample,
> _PyUnicode_FromStringAndSize(node->ms.sym->name,
> node->ms.sym->namelen));
> pydict_set_item_string_decref(pyelem, "sym", pysym);
> +
> + if (node->ms.map) {
> + struct map *map = node->ms.map;
> + struct addr_location node_al;
> + unsigned long offset;
> +
> + node_al.addr = map->map_ip(map, node->ip);
> + node_al.map = map;
> + offset = get_offset(node->ms.sym, &node_al);
> +
> + pydict_set_item_string_decref(
> + pyelem, "sym_off",
> + PyLong_FromUnsignedLongLong(offset));
> + }
> + if (node->srcline && strcmp(":0", node->srcline))
> + pydict_set_item_string_decref(
> + pyelem, "sym_srcline",
> + _PyUnicode_FromString(node->srcline));
nit missing { } for multiline if code
> }
>
> if (node->ms.map) {
> @@ -520,18 +550,6 @@ static PyObject *python_process_brstack(struct perf_sample *sample,
> return pylist;
> }
>
> -static unsigned long get_offset(struct symbol *sym, struct addr_location *al)
> -{
> - unsigned long offset;
> -
> - if (al->addr < sym->end)
> - offset = al->addr - sym->start;
> - else
> - offset = al->addr - al->map->start - sym->start;
> -
> - return offset;
> -}
> -
> static int get_symoff(struct symbol *sym, struct addr_location *al,
> bool print_off, char *bf, int size)
> {
>
next prev parent reply other threads:[~2022-02-10 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 14:44 [PATCH] perf scripting python: expose symbol offset and source information Eelco Chaudron
2022-02-10 7:52 ` Jiri Olsa [this message]
2022-02-22 15:05 ` Eelco Chaudron
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=YgTENKDfI/2+DZhJ@krava \
--to=olsajiri@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=echaudro@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--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