qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: yong.huang@smartx.com
To: qemu-devel <qemu-devel@nongnu.org>
Cc: "Fabiano Rosas" <farosas@suse.de>, "Peter Xu" <peterx@redhat.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Hyman Huang" <yong.huang@smartx.com>
Subject: [PATCH v4 RESEND 0/4] Guestperf: miscellaneous refinement and enrichment
Date: Fri, 14 Feb 2025 18:55:22 +0800	[thread overview]
Message-ID: <cover.1739530098.git.yong.huang@smartx.com> (raw)

From: Hyman Huang <yong.huang@smartx.com>

v4:
1. rebase v3 patchset on master
2. build initrd-stress.img manually like before as suggested by Peter and Fabiano
3. drop the [PATCH v3 1/5], [PATCH v3 2/5] patches
4. add an extra patch: [PATCH v4 4/4] guestperf: Add test result data into report

Please review, thanks
Yong

v3:
1. Remove the two redundant assignments in [PATCH v2 2/5] suggested by Daniel

v2:
1. Update the MAINTAINERS section suggested by Fabiano Rosas
2. Ensure the dependencies when build the initrd-stress.img suggested by Daniel
3. Fix some bugs

v1:
The previous patchset:
https://lore.kernel.org/qemu-devel/cover.1722957352.git.yong.huang@smartx.com/
does not made the necessary changes and tests for the upstream version.

This patchset works for that:
1. Move the guestperf to scripts directory suggested by Fabiano Rosas
2. Make initrd-stress.img built by default suggested by Fabiano Rosas
3. Make the necessary changes to adapt the latest multifd behavior
4. A nitpick for multifd migration
5. Support multifd compression option

Hyman Huang (4):
  guestperf: Support deferred migration for multifd
  guestperf: Nitpick the inconsistent parameters
  guestperf: Introduce multifd compression option
  guestperf: Add test result data into report

 .../migration-stress/guestperf/comparison.py  | 15 ++++++-
 tests/migration-stress/guestperf/engine.py    | 43 ++++++++++++++++---
 tests/migration-stress/guestperf/report.py    | 20 +++++++++
 tests/migration-stress/guestperf/scenario.py  |  7 ++-
 tests/migration-stress/guestperf/shell.py     |  3 ++
 5 files changed, 79 insertions(+), 9 deletions(-)

-- 
2.27.0



             reply	other threads:[~2025-02-14 10:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14 10:55 yong.huang [this message]
2025-02-14 10:55 ` [PATCH v4 RESEND 1/4] guestperf: Support deferred migration for multifd yong.huang
2025-02-14 10:55 ` [PATCH v4 RESEND 2/4] guestperf: Nitpick the inconsistent parameters yong.huang
2025-02-14 10:55 ` [PATCH v4 RESEND 3/4] guestperf: Introduce multifd compression option yong.huang
2025-02-14 10:55 ` [PATCH v4 RESEND 4/4] guestperf: Add test result data into report yong.huang
2025-02-14 14:26   ` Fabiano Rosas
2025-02-14 18:13 ` [PATCH v4 RESEND 0/4] Guestperf: miscellaneous refinement and enrichment Fabiano Rosas

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.1739530098.git.yong.huang@smartx.com \
    --to=yong.huang@smartx.com \
    --cc=berrange@redhat.com \
    --cc=farosas@suse.de \
    --cc=peterx@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 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).