qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Alex Bradbury <asb@igalia.com>
Cc: qemu-devel@nongnu.org,  erdnaxe@crans.org,
	 ma.mandourr@gmail.com, pierrick.bouvier@linaro.org
Subject: Re: [PATCH v2 0/5] contrib/plugins/hotblocks: Minor bug fixes and add limit argument
Date: Tue, 09 Dec 2025 16:18:34 +0000	[thread overview]
Message-ID: <874ipzwrvp.fsf@draig.linaro.org> (raw)
In-Reply-To: <6955a4f0a032b68a2b9fb1d1b6a7b620@igalia.com> (Alex Bradbury's message of "Tue, 09 Dec 2025 07:10:12 +0000")

Alex Bradbury <asb@igalia.com> writes:

> On 2025-12-02 23:05, Alex Bradbury wrote:
>> 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(-)
>
> Sending a ping as per the guidance at
> <https://www.qemu.org/docs/master/devel/submitting-a-patch.html#if-your-patch-seems-to-have-been-ignored>,
> and also linking to the patch on lore.kernel.org as that page suggests
> <https://lore.kernel.org/qemu-devel/cover.1764716538.git.asb@igalia.com/>

Sorry I missed this in v1. As we are getting very close to 10.2 getting
out of the door I'll punt this until the tree re-opens. I have it on my
backlog now.

If you want I can also cc qemu-stable if you think its worth having the
cleanups in 10.2.1

>
> Thanks.
>
> Alex

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2025-12-09 16:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 23:05 [PATCH v2 0/5] contrib/plugins/hotblocks: Minor bug fixes and add limit argument Alex Bradbury
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 [this message]
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=874ipzwrvp.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=asb@igalia.com \
    --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).