From: Bibo Mao <maobibo@loongson.cn>
To: Song Gao <gaosong@loongson.cn>, Peter Xu <peterx@redhat.com>,
Fabiano Rosas <farosas@suse.de>, Thomas Huth <thuth@redhat.com>,
Laurent Vivier <lvivier@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: [PATCH v4 0/5] Add migration test for loongarch64
Date: Wed, 8 May 2024 11:11:05 +0800 [thread overview]
Message-ID: <20240508031110.2507477-1-maobibo@loongson.cn> (raw)
Migration test case is added for loongarch64 here. Since compat machine
type is required for migration test case, also compat machine qemu 9.0
is added for loongarch virt machine.
Migration test case passes to run in both tcg and kvm mode with the
patch, 54 migration subtests passes in 188 seconds.
---
v3 ... v4:
1. Rename VIRT_MACHINE with LOONGARCH_VIRT_MACHINE since other
architectures have the same machine type.
v2 ... v3:
1. Refresh the patch based on the latest qemu version, solve the
confliction issue.
v1 ... v2:
1. Keep the default memory size unchanged with 1GB, only modify minimum
memory size with 256MB
2. Remove tab char in file tests/migration/loongarch64/a-b-kernel.S
---
Bibo Mao (5):
hw/loongarch: Rename LOONGARCH_MACHINE with LOONGARCH_VIRT_MACHINE
hw/loongarch: Rename LoongArchMachineState with
LoongArchVirtMachineState
hw/loongarch: Add compat machine for 9.0
hw/loongarch: Set minimium memory size as 256M
tests: Add migration test for loongarch64
hw/loongarch/acpi-build.c | 88 ++---
hw/loongarch/boot.c | 10 +-
hw/loongarch/fw_cfg.c | 2 +-
hw/loongarch/fw_cfg.h | 2 +-
hw/loongarch/virt.c | 393 ++++++++++++-----------
include/hw/loongarch/virt.h | 9 +-
tests/migration/Makefile | 2 +-
tests/migration/loongarch64/Makefile | 18 ++
tests/migration/loongarch64/a-b-kernel.S | 49 +++
tests/migration/loongarch64/a-b-kernel.h | 16 +
tests/migration/migration-test.h | 3 +
tests/qtest/meson.build | 4 +
tests/qtest/migration-test.c | 10 +
13 files changed, 370 insertions(+), 236 deletions(-)
create mode 100644 tests/migration/loongarch64/Makefile
create mode 100644 tests/migration/loongarch64/a-b-kernel.S
create mode 100644 tests/migration/loongarch64/a-b-kernel.h
base-commit: 4e66a08546a2588a4667766a1edab9caccf24ce3
--
2.39.3
next reply other threads:[~2024-05-08 3:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 3:11 Bibo Mao [this message]
2024-05-08 3:11 ` [PATCH v4 1/5] hw/loongarch: Rename LOONGARCH_MACHINE with LOONGARCH_VIRT_MACHINE Bibo Mao
2024-05-08 15:08 ` Philippe Mathieu-Daudé
2024-05-08 3:11 ` [PATCH v4 2/5] hw/loongarch: Rename LoongArchMachineState with LoongArchVirtMachineState Bibo Mao
2024-05-08 15:08 ` Philippe Mathieu-Daudé
2024-05-08 3:11 ` [PATCH v4 3/5] hw/loongarch: Add compat machine for 9.0 Bibo Mao
2024-05-08 3:11 ` [PATCH v4 4/5] hw/loongarch: Set minimium memory size as 256M Bibo Mao
2024-05-08 3:11 ` [PATCH v4 5/5] tests: Add migration test for loongarch64 Bibo Mao
2024-05-08 21:58 ` [PATCH v4 0/5] " Philippe Mathieu-Daudé
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=20240508031110.2507477-1-maobibo@loongson.cn \
--to=maobibo@loongson.cn \
--cc=farosas@suse.de \
--cc=gaosong@loongson.cn \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).