From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>,
Richard Henderson <richard.henderson@linaro.org>
Cc: "Vanderson M . do Rosario" <vandersonmr2@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 1/1] tcg: add perfmap and jitdump
Date: Fri, 28 Oct 2022 10:39:57 +0200 [thread overview]
Message-ID: <e9ef8994-672f-65c4-8b93-d163a8b90cae@linux.ibm.com> (raw)
In-Reply-To: <20221012051846.1432050-2-iii@linux.ibm.com>
Am 12.10.22 um 07:18 schrieb Ilya Leoshkevich:
> Add ability to dump /tmp/perf-<pid>.map and jit-<pid>.dump.
> The first one allows the perf tool to map samples to each individual
> translation block. The second one adds the ability to resolve symbol
> names, line numbers and inspect JITed code.
>
> Example of use:
>
> perf record qemu-x86_64 -perfmap ./a.out
> perf report
>
> or
>
> perf record -k 1 qemu-x86_64 -jitdump ./a.out
> perf inject -j -i perf.data -o perf.data.jitted
> perf report -i perf.data.jitted
>
> Co-developed-by: Vanderson M. do Rosario <vandersonmr2@gmail.com>
> Co-developed-by: Alex Bennée <alex.bennee@linaro.org>
> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
I think this would be awesome to have. I know our performance people do use this for Java a lot.
next prev parent reply other threads:[~2022-10-28 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 5:18 [PATCH RFC 0/1] tcg: add perfmap and jitdump Ilya Leoshkevich
2022-10-12 5:18 ` [PATCH 1/1] " Ilya Leoshkevich
2022-10-13 20:35 ` Richard Henderson
2022-10-18 2:22 ` Ilya Leoshkevich
2022-10-28 8:39 ` Christian Borntraeger [this message]
2022-11-07 11:04 ` Alex Bennée
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=e9ef8994-672f-65c4-8b93-d163a8b90cae@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=alex.bennee@linaro.org \
--cc=iii@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=vandersonmr2@gmail.com \
/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).