qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Bradbury <asb@igalia.com>
To: qemu-devel@nongnu.org
Cc: Alex Bradbury <asb@igalia.com>,
	alex.bennee@linaro.org, erdnaxe@crans.org, ma.mandourr@gmail.com,
	pierrick.bouvier@linaro.org
Subject: [PATCH v2 0/5] contrib/plugins/hotblocks: Minor bug fixes and add limit argument
Date: Tue,  2 Dec 2025 23:05:53 +0000	[thread overview]
Message-ID: <cover.1764716538.git.asb@igalia.com> (raw)

This is a resend of my previous patchset which unfortunately seems not to have
been applied (see
<https://lore.kernel.org/qemu-devel/cover.1753857212.git.asb@igalia.com/).
I've rebased on current HEAD, checked it works as expected, and added
Reviewed-by tags to the patches, which all received review.

Repeating the summary from last time:

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.

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(-)

-- 
2.52.0



             reply	other threads:[~2025-12-02 23:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 23:05 Alex Bradbury [this message]
2025-12-02 23:05 ` [PATCH v2 1/5] contrib/plugins/hotblocks: Correctly free sorted counts list Alex Bradbury
2025-12-02 23:05 ` [PATCH v2 2/5] contrib/plugins/hotblocks: Fix off by one error in iteration of sorted blocks Alex Bradbury
2025-12-02 23:05 ` [PATCH v2 3/5] contrib/plugins/hotblocks: Print uint64_t with PRIu64 rather than PRId64 Alex Bradbury
2025-12-02 23:05 ` [PATCH v2 4/5] docs/about/emulation: Add documentation for hotblocks plugin arguments Alex Bradbury
2025-12-02 23:05 ` [PATCH v2 5/5] contrib/plugins/hotblocks: Allow limit to be set as a command line argument Alex Bradbury
2025-12-03  2:03 ` [PATCH v2 0/5] contrib/plugins/hotblocks: Minor bug fixes and add limit argument Pierrick Bouvier
2025-12-09  7:10 ` Alex Bradbury
2025-12-09 16:18   ` Alex Bennée
2025-12-12 12:00 ` 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=cover.1764716538.git.asb@igalia.com \
    --to=asb@igalia.com \
    --cc=alex.bennee@linaro.org \
    --cc=erdnaxe@crans.org \
    --cc=ma.mandourr@gmail.com \
    --cc=pierrick.bouvier@linaro.org \
    --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).