From: Nicholas Piggin <npiggin@gmail.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: Nicholas Piggin <npiggin@gmail.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Thomas Huth <thuth@redhat.com>
Subject: [PATCH 0/3] tests/qtest/migration-test: Improve and enable on ppc64
Date: Sat, 25 May 2024 13:13:26 +1000 [thread overview]
Message-ID: <20240525031330.196609-1-npiggin@gmail.com> (raw)
ppc64 seems to be stable now, only problem is the speed, so I
rewrote the test to avoid SLOF and use special bios blob like
the other archs.
Thanks,
Nick
Nicholas Piggin (3):
tests/qtest/migration-test: Quieten ppc64 QEMU warnigns
tests/qtest/migration-test: Enable on ppc64
tests/qtest/migration-test: Use custom asm bios for ppc64
tests/migration/migration-test.h | 1 +
tests/migration/ppc64/a-b-kernel.h | 42 +++++++++++++++++++
tests/qtest/migration-test.c | 53 +++++-------------------
tests/migration/Makefile | 2 +-
tests/migration/ppc64/Makefile | 15 +++++++
tests/migration/ppc64/a-b-kernel.S | 66 ++++++++++++++++++++++++++++++
6 files changed, 135 insertions(+), 44 deletions(-)
create mode 100644 tests/migration/ppc64/a-b-kernel.h
create mode 100644 tests/migration/ppc64/Makefile
create mode 100644 tests/migration/ppc64/a-b-kernel.S
--
2.43.0
next reply other threads:[~2024-05-25 3:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 3:13 Nicholas Piggin [this message]
2024-05-25 3:13 ` [PATCH 1/3] tests/qtest/migration-test: Quieten ppc64 QEMU warnigns Nicholas Piggin
2024-05-27 7:32 ` Thomas Huth
2024-05-27 11:26 ` Nicholas Piggin
2024-05-27 11:37 ` Thomas Huth
2024-05-25 3:13 ` [PATCH 2/3] tests/qtest/migration-test: Enable on ppc64 Nicholas Piggin
2024-05-27 7:35 ` Thomas Huth
2024-05-27 11:27 ` Nicholas Piggin
2024-05-25 3:13 ` [PATCH 3/3] tests/qtest/migration-test: Use custom asm bios for ppc64 Nicholas Piggin
2024-05-27 13:01 ` 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=20240525031330.196609-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=farosas@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/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.