From: Peter Xu <peterx@redhat.com>
To: Ani Sinha <anisinha@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@mailo.com>,
agraf@csgraf.de, graf@amazon.com, qemu-devel@nongnu.org,
kraxel@redhat.com
Subject: Re: [PATCH v4 04/11] system/memory: add a tracepoint for memory_region_finalize
Date: Fri, 7 Aug 2026 08:59:11 -0400 [thread overview]
Message-ID: <anXWn4-q92ZUULDb@x1.local> (raw)
In-Reply-To: <20260807052559.50643-5-anisinha@redhat.com>
On Fri, Aug 07, 2026 at 10:55:46AM +0530, Ani Sinha wrote:
> cosmetic: add a tracepoint to track when memory regions are getting freed.
> Useful for debugging and tracking all freed memory regions.
>
> Signed-off-by: Ani Sinha <anisinha@redhat.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
next prev parent reply other threads:[~2026-08-07 13:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 5:25 [PATCH v4 00/11] Introducing guest driven VM launch update mechanism (BYOF interface) Ani Sinha
2026-08-07 5:25 ` [PATCH v4 01/11] igvm: store IgvmCfg pointer in QIgvm Ani Sinha
2026-08-07 5:25 ` [PATCH v4 02/11] igvm: track memory regions Ani Sinha
2026-08-07 5:25 ` [PATCH v4 03/11] igvm: cleanup " Ani Sinha
2026-08-07 5:25 ` [PATCH v4 04/11] system/memory: add a tracepoint for memory_region_finalize Ani Sinha
2026-08-07 12:59 ` Peter Xu [this message]
2026-08-07 5:25 ` [PATCH v4 05/11] backends/igvm: add a tracepoint for qigvm_cleanup_memory Ani Sinha
2026-08-07 5:25 ` [PATCH v4 06/11] hw/misc/vmlaunchupdate: add api header Ani Sinha
2026-08-07 5:25 ` [PATCH v4 07/11] hw/misc/vmlaunchupdate: Introduce hypervisor fw-cfg interface support Ani Sinha
2026-08-07 5:25 ` [PATCH v4 08/11] docs/spec: Add a specification document for vm-launch-update device Ani Sinha
2026-08-07 5:25 ` [PATCH v4 09/11] tests/qtest: Add small igvm files for testing purpose Ani Sinha
2026-08-07 5:25 ` [PATCH v4 10/11] Add functional and unit tests for the vm-launch-update device Ani Sinha
2026-08-07 5:25 ` [PATCH v4 11/11] Update MAINTAINERS Ani Sinha
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=anXWn4-q92ZUULDb@x1.local \
--to=peterx@redhat.com \
--cc=agraf@csgraf.de \
--cc=anisinha@redhat.com \
--cc=graf@amazon.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@mailo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.