From: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
To: vandersonmr <vandersonmr2@gmail.com>
Cc: Riku Voipio <riku.voipio@iki.fi>,
qemu-devel@nongnu.org, Laurent Vivier <laurent@vivier.eu>
Subject: Re: [Qemu-devel] [PATCH v5 10/10] linux-user: dumping hot TBs at the end of the execution
Date: Thu, 15 Aug 2019 16:26:14 +0200 [thread overview]
Message-ID: <CAL1e-=jTfUidZmHQy0kpjZk49FDAvX91y8SM3FDyHmPyG7qKrA@mail.gmail.com> (raw)
In-Reply-To: <20190815021857.19526-11-vandersonmr2@gmail.com>
15.08.2019. 04.37, "vandersonmr" <vandersonmr2@gmail.com> је написао/ла:
>
> dumps, in linux-user mode, the hottest TBs if -d tb_stats is used.
>
> Signed-off-by: Vanderson M. do Rosario <vandersonmr2@gmail.com>
> --
Hi, Vanderson,
Can you please provide an illustrative example of the dump output, within
the commit message?
Thanks,
Aleksandar
> linux-user/exit.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/linux-user/exit.c b/linux-user/exit.c
> index bdda720553..7226104959 100644
> --- a/linux-user/exit.c
> +++ b/linux-user/exit.c
> @@ -28,6 +28,10 @@ extern void __gcov_dump(void);
>
> void preexit_cleanup(CPUArchState *env, int code)
> {
> + if (tb_stats_collection_enabled()) {
> + dump_tbs_info(max_num_hot_tbs_to_dump, SORT_BY_HOTNESS, false);
> + }
> +
> #ifdef TARGET_GPROF
> _mcleanup();
> #endif
> --
> 2.22.0
>
>
prev parent reply other threads:[~2019-08-15 14:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 2:18 [Qemu-devel] [PATCH v5 00/10] Measure Tiny Code Generation Quality vandersonmr
2019-08-15 2:18 ` [Qemu-devel] [PATCH v5 01/10] accel: introducing TBStatistics structure vandersonmr
2019-08-15 13:13 ` Alex Bennée
2019-08-15 2:18 ` [Qemu-devel] [PATCH v5 02/10] accel: collecting TB execution count vandersonmr
2019-08-15 13:38 ` Alex Bennée
2019-08-15 2:18 ` [Qemu-devel] [PATCH v5 03/10] accel: collecting JIT statistics vandersonmr
2019-08-15 14:29 ` Alex Bennée
2019-08-15 2:18 ` [Qemu-devel] [PATCH v5 04/10] accel: replacing part of CONFIG_PROFILER with TBStats vandersonmr
2019-08-15 14:54 ` Alex Bennée
2019-08-15 2:18 ` [Qemu-devel] [PATCH v5 05/10] accel: adding TB_JIT_TIME and full replacing CONFIG_PROFILER vandersonmr
2019-08-15 2:18 ` [Qemu-devel] [PATCH v5 06/10] log: adding -d tb_stats to control tbstats vandersonmr
2019-08-15 2:18 ` [Qemu-devel] [PATCH v5 07/10] monitor: adding tb_stats hmp command vandersonmr
2019-08-15 8:53 ` Dr. David Alan Gilbert
2019-08-15 2:18 ` [Qemu-devel] [PATCH v5 08/10] Adding info [tbs|tb|coverset] commands to HMP. These commands allow the exploration of TBs generated by the TCG. Understand which one hotter, with more guest/host instructions... and examine their guest, host and IR code vandersonmr
2019-08-15 8:59 ` Dr. David Alan Gilbert
2019-08-21 14:16 ` Vanderson Martins do Rosario
2019-08-21 14:29 ` Dr. David Alan Gilbert
2019-08-15 2:18 ` [Qemu-devel] [PATCH v5 09/10] monitor: adding new info cfg command vandersonmr
2019-08-15 9:14 ` Dr. David Alan Gilbert
2019-08-15 2:18 ` [Qemu-devel] [PATCH v5 10/10] linux-user: dumping hot TBs at the end of the execution vandersonmr
2019-08-15 14:26 ` Aleksandar Markovic [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='CAL1e-=jTfUidZmHQy0kpjZk49FDAvX91y8SM3FDyHmPyG7qKrA@mail.gmail.com' \
--to=aleksandar.m.mail@gmail.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--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).