From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Prasad Pandit <ppandit@redhat.com>,
Fabiano Rosas <farosas@suse.de>, Bandan Das <bdas@redhat.com>,
Julia Suvorova <jusual@redhat.com>
Subject: Re: [PATCH 0/3] migration: some small cleanups
Date: Sat, 20 Jan 2024 10:36:34 +0800 [thread overview]
Message-ID: <Zasxsn8rfHUlecHM@x1n> (raw)
In-Reply-To: <20240117075848.139045-1-peterx@redhat.com>
On Wed, Jan 17, 2024 at 03:58:45PM +0800, peterx@redhat.com wrote:
> From: Peter Xu <peterx@redhat.com>
>
> I found three tiny little patches lying around probably for a long time,
> sending it out before deleting the branch. Review welcomed, thanks.
>
> Peter Xu (3):
> migration: Make threshold_size an uint64_t
> migration: Drop unnecessary check in ram's pending_exact()
> analyze-migration.py: Remove trick on parsing ramblocks
>
> migration/migration.h | 2 +-
> migration/ram.c | 9 ++++-----
> scripts/analyze-migration.py | 11 +++--------
> 3 files changed, 8 insertions(+), 14 deletions(-)
queued.
--
Peter Xu
prev parent reply other threads:[~2024-01-20 2:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 7:58 [PATCH 0/3] migration: some small cleanups peterx
2024-01-17 7:58 ` [PATCH 1/3] migration: Make threshold_size an uint64_t peterx
2024-01-17 8:09 ` Philippe Mathieu-Daudé
2024-01-19 13:26 ` Fabiano Rosas
2024-01-17 7:58 ` [PATCH 2/3] migration: Drop unnecessary check in ram's pending_exact() peterx
2024-01-19 13:25 ` Fabiano Rosas
2024-03-20 17:51 ` Nina Schoetterl-Glausch
2024-03-20 18:05 ` Nina Schoetterl-Glausch
2024-03-20 18:57 ` Peter Xu
2024-03-20 19:21 ` Nina Schoetterl-Glausch
2024-03-20 19:46 ` Peter Xu
2024-03-20 20:45 ` Peter Xu
2024-01-17 7:58 ` [PATCH 3/3] analyze-migration.py: Remove trick on parsing ramblocks peterx
2024-01-19 13:23 ` Fabiano Rosas
2024-01-20 2:36 ` Peter Xu [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=Zasxsn8rfHUlecHM@x1n \
--to=peterx@redhat.com \
--cc=bdas@redhat.com \
--cc=farosas@suse.de \
--cc=jusual@redhat.com \
--cc=ppandit@redhat.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.