From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: Alex Bradbury <asb@igalia.com>, qemu-devel@nongnu.org
Cc: alex.bennee@linaro.org, erdnaxe@crans.org, ma.mandourr@gmail.com
Subject: Re: [PATCH 0/5] contrib/plugins/hotblocks: Minor bug fixes and add limit argument
Date: Wed, 30 Jul 2025 10:48:51 -0700 [thread overview]
Message-ID: <aa061a96-8552-45e6-b5a5-af12d35332ba@linaro.org> (raw)
In-Reply-To: <cover.1753857212.git.asb@igalia.com>
On 7/29/25 11:41 PM, Alex Bradbury wrote:
> This series contains one minor feature addition and a series of small
> bugfixes/improvements. The addition that motivates the submission is to add a
> limit argument for the hotblocks plugin, allowing you to control how many
> blocks are printed rather than being hardcoded to the 20 most executed.
> Setting limit=0 and dumping information about all executed blocks is
> incredibly helpful for an analysis script I have downstream.
>
> This is my first contribution to QEMU. I've attempted to follow all of the
> guidance in the "Submitting a Patch" guide, but apologies if I missed
> anything.
>
Thanks for contributing Alex.
As you probably read, in case a v2 is expected (the plugins maintainer
Alex will be back next week, he might have additional comments), you can
add the "Reviewed-by" tags you already collected to your commits by
ammending their messages.
For the rest, your series looks good to me.
Regards,
Pierrick
> Alex Bradbury (5):
> contrib/plugins/hotblocks: Correctly free sorted counts list
> contrib/plugins/hotblocks: Fix off by one error in iteration of sorted
> blocks
> contrib/plugins/hotblocks: Print uint64_t with PRIu64 rather than
> PRId64
> docs/about/emulation: Add documentation for hotblocks plugin arguments
> contrib/plugins/hotblocks: Allow limit to be set as a command line
> argument
>
> contrib/plugins/hotblocks.c | 20 ++++++++++++++------
> docs/about/emulation.rst | 12 ++++++++++++
> 2 files changed, 26 insertions(+), 6 deletions(-)
>
prev parent reply other threads:[~2025-07-30 19:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 6:41 [PATCH 0/5] contrib/plugins/hotblocks: Minor bug fixes and add limit argument Alex Bradbury
2025-07-30 6:41 ` [PATCH 1/5] contrib/plugins/hotblocks: Correctly free sorted counts list Alex Bradbury
2025-07-30 14:03 ` Manos Pitsidianakis
2025-07-30 17:44 ` Pierrick Bouvier
2025-07-30 6:41 ` [PATCH 2/5] contrib/plugins/hotblocks: Fix off by one error in iteration of sorted blocks Alex Bradbury
2025-07-30 17:45 ` Pierrick Bouvier
2025-07-30 6:41 ` [PATCH 3/5] contrib/plugins/hotblocks: Print uint64_t with PRIu64 rather than PRId64 Alex Bradbury
2025-07-30 13:32 ` Manos Pitsidianakis
2025-07-30 17:46 ` Pierrick Bouvier
2025-07-30 6:41 ` [PATCH 4/5] docs/about/emulation: Add documentation for hotblocks plugin arguments Alex Bradbury
2025-07-30 17:46 ` Pierrick Bouvier
2025-07-30 6:41 ` [PATCH 5/5] contrib/plugins/hotblocks: Allow limit to be set as a command line argument Alex Bradbury
2025-07-30 17:52 ` Pierrick Bouvier
2025-07-30 13:48 ` [PATCH 0/5] contrib/plugins/hotblocks: Minor bug fixes and add limit argument Manos Pitsidianakis
2025-07-30 13:54 ` Alex Bradbury
2025-07-30 17:50 ` Pierrick Bouvier
2025-07-30 17:48 ` Pierrick Bouvier [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=aa061a96-8552-45e6-b5a5-af12d35332ba@linaro.org \
--to=pierrick.bouvier@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=asb@igalia.com \
--cc=erdnaxe@crans.org \
--cc=ma.mandourr@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).